rdma_set_service_type(9)

💅 NAME 💅

Okay bestie, welcome to rdma_set_service_type(9) from the Kernel API Manual — this one is literally all about setting the type of service associated with a connection identifier. No cap. ✨

🎀 SYNOPSIS 🎀

void rdma_set_service_type (struct rdma_cm_id *id , int tos );

🦋 ARGUMENTS 🦋

• id — the communication identifier you're associating with the service type. 🫶
• tos — the type of service. That's the whole vibe. 💅

🌸 DESCRIPTION 🌸

So the type of service is interpretted as a differentiated service field (RFC 2474). Slay. 🧚

Set that service type before you perform route resolution, okay? Because existing communication on the connection identifier may be unaffected — like, the traffic already out there is not necessarily gonna get the memo. 😭

Also, fair warning: the type of service you request may not be supported by the network to all destinations. It's giving "best effort, not a guarantee," and you should not act brand new about it. 💀

🌈 SEE ALSO 🌈

Kernel file ./include/rdma/rdma_cm.h, plus the whole squad: rdma_create_id(9), rdma_destroy_id(9), rdma_restrict_node_type(9), rdma_bind_addr(9), rdma_resolve_addr(9), rdma_resolve_route(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_reuseaddr(9), rdma_set_afonly(9), rdma_reject_msg(9), rdma_consumer_reject_data(9), rdma_read_gids(9). 👑

Source/version: ./include/rdma · Date: October 2026 · Page: rdma_set_service_type(9) — periodt, bestie, that's the whole page. 💖