STRUCT NVME_RDMA_CM_REJ(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… struct nvme_rdma_cm_rej(9) β€” from the Kernel API Manual, bestie πŸŽ€

okay so picture this: you're deep in the kernel, doing RDMA things, and somebody's connect request just did NOT work out. this little struct is literally the "hey bestie, it's not happening" note. it's the rdma connect reject ✨


🌸 NAME 🌸

struct nvme_rdma_cm_rej β€” rdma connect reject. that's it, that's the vibe. it's giving rejection letter but make it kernel πŸ’Œ


✨ SYNOPSIS ✨

struct nvme_rdma_cm_rej {
    __le16 recfmt;
    __le16 sts;
 };

two fields. tiny struct. main character energy in like eight lines of C 🫢


πŸ¦‹ Members πŸ¦‹

okay let's meet the cast:

  • recfmt β€” the format of the RDMA Private Data. it's telling you how the private data is laid out, iykyk πŸ“‹
  • sts β€” the error status for the associated connect request. this is the why of the rejection, the actual receipts 😭
no cap, that's the whole struct. two little __le16 fields carrying the entire "nope" of a failed connection. iconic behavior honestly πŸ‘‘

πŸ”₯ SEE ALSO πŸ”₯

  • Kernel file ./include/linux/nvme-rdma.h
  • struct nvme_rdma_cm_req(9) β€” the request that started it all πŸ’«
  • struct nvme_rdma_cm_rep(9) β€” the reply side of the story 🌈

and that's the page! fr fr, go read the header file if you want the full lore πŸ“–

source path ./include/linux, dated October 2026, page struct nvme_rdma_cm_rej(9) β€” mwah, sending you off with a πŸŽ€ and a πŸ’–, now go slay those RDMA connections bestie πŸ’…βœ¨

πŸ“¦ where this page comes from