rdma_resolve_route(9)

💖 rdma_resolve_route(9) 💖

okay so bestie, this is rdma_resolve_route(9) from the Kernel API Manual — section 9, pulling up with main-character energy. It's literally about resolving the RDMA address bound to the RDMA identifier into route information needed to establish a connection. slay. ✨

🌸 NAME 🌸

rdma_resolve_route — resolve the RDMA address bound to the RDMA identifier into route information needed to establish a connection. That's the whole name-section flex, no cap. 🦋

✨ SYNOPSIS ✨

int rdma_resolve_route (struct rdma_cm_id *id , unsigned long timeout_ms
       );

🎀 ARGUMENTS 🎀

• id — -- undescribed -- 😭 the page itself says it, bestie, so I'm not out here inventing lore.
• timeout_ms — -- undescribed -- 🫶 same energy, same mystery, same exact placeholder.

💅 DESCRIPTION 💅

This is called on the client side of a connection. periodt. 💖

Users must have first called rdma_resolve_addr to resolve a dst_addr into an RDMA address before calling this routine. That's the prerequisite, bestie — don't skip the prequel. ✨

🦋 SEE ALSO 🦋

Kernel file ./include/rdma/rdma_cm.h — and then the whole squad is:

• rdma_create_id(9)
• rdma_destroy_id(9)
• rdma_restrict_node_type(9)
• rdma_bind_addr(9)
• rdma_resolve_addr(9)
• rdma_resolve_ib_service(9)
• rdma_create_qp(9)
• rdma_destroy_qp(9)
• rdma_init_qp_attr(9)
• rdma_listen(9)
• rdma_notify(9)
• rdma_reject(9)
• rdma_disconnect(9)
• rdma_join_multicast(9)
• rdma_leave_multicast(9)
• rdma_set_service_type(9)
• rdma_set_reuseaddr(9)
• rdma_set_afonly(9)
• rdma_reject_msg(9)
• rdma_consumer_reject_data(9)
• rdma_read_gids(9)

🫶 mwah, that's the page! Source/version: ./include/rdma · date: October 2026 · page: rdma_resolve_route(9). 💋