bnxt_qplib_r...send_message(9)

💅 NAME 💅

bnxt_qplib_rcfw_send_message — the qplib interface bestie that sends and completes rcfw commands, no cap ✨

Oh and btw, this whole page lives under the manual name bnxt_qplib_r...send_message(9) — that's the header energy, keeping it iconic 🎀

---

🌸 SYNOPSIS 🌸

int bnxt_qplib_rcfw_send_message (struct bnxt_qplib_rcfw *rcfw , struct
       bnxt_qplib_cmdqmsg *msg );

---

🦋 ARGUMENTS 🦋

• rcfw — the rcfw channel instance of rdev 🫶 that's literally the whole vibe, it's the channel babe
• msg — a qplib message, internal ✨ very inside-the-house, not for outside consumption

---

👑 DESCRIPTION 👑

okay so picture this: the driver talks to the Firmware through the rcfw channel / slow path, and it does it in two ways, and both of them are valid, periodt 💅

1. Blocking rcfw command send. In this path the driver cannot hold the context for a longer period — because it is literally holding the cpu until the command is completed 😭 like it's stuck there, waiting, no escape
2. Non-blocking rcfw command send. In this path the driver can hold the context for a longer period 🌈 but here's the tea: there may be many pending commands just waiting for completion, because of that whole non-blocking nature of it 🙈

The driver is gonna use a shadow queue depth, and this is where it gets juicy. The current queue depth is 8K — and because of the size of the rcfw message there can be actual ~4K rcfw outstanding — and ngl that is not optimal for rcfw command processing in firmware 💀 it's giving bottleneck

So: restrict at max #RCFW_CMD_NON_BLOCKING_SHADOW_QD Non-Blocking rcfw commands. That's the ceiling bestie, we do not go past it 🚧

And allow all blocking commands until there is no queue full ✨ blocking ones get the whole run of the place, they're the main characters here 👑

---

💖 RETURN 💖

• 0 — if the command was completed by firmware 🎉 slay, we love a completion
• Non zero — if the command is not completed by firmware 😭 it's giving unfinished business

---

🌟 SEE ALSO 🌟

• Kernel file ./drivers/infiniband/hw/bnxt_re/qplib_rcfw.c — go read the source bestie, it's right there 📖
• bnxt_qplib_map_rc(9)
• bnxt_re_is_fw_stalled(9)
• __wait_for_resp(9)
• __block_for_resp(9)
• __poll_for_resp(9)
• __bnxt_qplib_rcfw_send_message(9)

iykyk, the underscores ones are the ✨inner circle✨ fr fr

---

ok that's the whole page, no notes 💅 go forth and send those messages, blocking or non-blocking, you got this 🫶

---

and that's a wrap bestie 🎀 this was brought to you by ./drivers/infiniband/hw/bnxt_re, dated October 2026, living under the name bnxt_qplib_r...send_message(9) — mwah, see you in the source 💜🔥