bng_re_map_rc(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… bng_re_map_rc(9) β€” the Kernel API Manual cut πŸ’…

okay so bestie, welcome to the bng_re_map_rc page from the Kernel API Manual β€” yes that's the manual name, we're folding it in at the top like a little name tag πŸŽ€ this whole page is about one tiny helper that maps a return type based on an opcode, and honestly it's giving "small function, big feelings" ✨


✨ NAME ✨

bng_re_map_rc β€” map return type based on opcode</p> πŸ’– that's it, that's the whole job, no cap.


🌸 SYNOPSIS 🌸

int bng_re_map_rc (u8 opcode );

so we're returning an int, and we're taking exactly one u8 called opcode. cute, clean, iconic πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • opcode β€” roce slow path opcode 🫢 that's the thing you're handing in, and it's literally the whole vibe check for this function

πŸ”₯ DESCRIPTION πŸ”₯

okay so here's the lore, and it comes in two cases β€” the way that the driver can be in two completely different moods 😭

  1. case #1 β€” Firmware initiated error recovery is a safe state machine and the driver can consider all the underlying rdma resources are free. In this state, it is safe to return success for opcodes related to destroying rdma resources (like destroy qp, destroy cq etc.). ✨
  2. case #2 β€” If the driver detects a potential firmware stall, it is not a safe state machine and the driver can not consider all the underlying rdma resources are freed. In this state, it is not safe to return success for opcodes related to destroying rdma resources (like destroy qp, destroy cq etc.). πŸ’€
🚨 and here's the part you cannot miss, bestie: Scope of this helper function is only for case #1. only case #1. not case #2. do not come for case #2 with this function, fr fr πŸ™ˆ

πŸ’œ RETURN πŸ’œ

  • 0 β€” communicates success to the caller 🌈
  • Non zero error code β€” communicates failure to the caller 😭

πŸŽ€ SEE ALSO πŸŽ€


and that's the page!! πŸ¦‹ the source lives over at ./drivers/infiniband/hw/bng_re, it's dated October 2026, and it's the bng_re_map_rc(9) page β€” go read the source, it's literally right there, iykyk πŸ’–βœ¨πŸŽ€

πŸ“¦ where this page comes from