irdma_vchnl_req_verify_resp(9)

💅 irdma_vchnl_req_verify_resp(9) — from the Kernel API Manual, section 9, bestie 🎀

okay so picture this: it's a kernel API Manual page, it's section 9, and the star of the show is irdma_vchnl_req_verify_resp — literally the vibe-check bouncer for response sizes. no cap, that's the whole job. ✨

---

✨ NAME ✨

irdma_vchnl_req_verify_resp — verify requested response size 🦋

like… it checks that the response size you asked for is, in fact, the size. she's giving quality control. she's giving "ma'am, that's not the length." 💅

---

🌸 SYNOPSIS 🌸

int irdma_vchnl_req_verify_resp(struct irdma_vchnl_req *vchnl_req, u16
       resp_len);

so she takes two things and hands you back an int. that's it. that's the whole signature, copied exactly, no notes. 🫶

---

🎀 ARGUMENTS 🎀

• vchnl_req — the vchnl message that got requested. yes bestie, this is THE message. the one we're checking up on. 👑
• resp_len — the response length that got sent over from the vchnl peer. this is the number under review. the accused, if you will. 😭

lowkey both of these are mandatory, and their types are struct irdma_vchnl_req * and u16 respectively — don't come at me with "can I pass something else," the answer is in the synopsis, iykyk. 💀

---

🌈 SEE ALSO 🌈

the kernel file where all the magic lives:

./drivers/infiniband/hw/irdma/virtchnl.c

and her whole friend group, fr fr — every single one, no gatekeeping:

• irdma_sc_vchnl_init(9)
• irdma_vchnl_req_get_reg_layout(9)
• irdma_vchnl_req_aeq_vec_map(9)
• irdma_vchnl_req_ceq_vec_map(9)
• irdma_vchnl_req_get_ver(9)
• irdma_vchnl_req_get_hmc_fcn(9)
• irdma_vchnl_req_put_hmc_fcn(9)
• irdma_vchnl_req_get_caps(9)
• irdma_vchnl_req_get_resp(9)

that's nine besties plus the source file. a whole squad. the group chat is POPPING. 🧚

---

and that's the page!! 🎉 shoutout to ./drivers/infiniband/hw/irdma for being the source, October 2026 for the date, and irdma_vchnl_req_verify_resp(9) for the version tag — mwah, iconic, periodt. 🍓💖🌸