bnx2i_arm_c...t_coalescing(9)

📦 version 7.3.1, in nixpkgs unstable

💅 bnx2i_arm_cq_event_coalescing(9) — from the Kernel API Manual, section 9, bestie ✨

okay so picture this: you're deep in the kernel, section 9 of the Kernel API Manual, and you need a CQ armed. This is that page. Let's get into it 🎀

✨ NAME ✨

bnx2i_arm_cq_event_coalescing — no cap, this is the one that arms CQ so EQ notifications can actually happen 💖

🌸 SYNOPSIS 🌸

int bnx2i_arm_cq_event_coalescing (struct bnx2i_endpoint *ep , u8 action );

she takes two things and returns an int, periodt. 🫶

🦋 ARGUMENTS 🦋

  • ep — the endpoint structure, aka the transport identifier. That's your girl. 🧚
  • action — the action, which is ARM or DISARM. Lowkey for now only ARM_CQE is used, so don't come for me about the rest 💀

🔥 DESCRIPTION 🔥

okay so Arm'ing the CQ is literally what enables the chip to generate global EQ events, which is how it interrupts the driver. It's giving "let the hardware speak" energy. 👑

The EQ event gets generated when the CQ index is hit, or when at least 1 CQ is outstanding and the on-chip timer expires. Both roads lead to interrupt town, iykyk ⏰✨

💜 SEE ALSO 💜

Kernel file ./drivers/scsi/bnx2i/bnx2i_hwi.c — and honestly the whole squad lives there too, so here's the full roll call (not me listing all of these, but every single one is iconic in her own way 😭):

go read the source, bestie — it's all right there in ./drivers/scsi/bnx2i 🌈

that's the whole vibe check, mwah 💋 this page came from ./drivers/scsi/bnx2i, dated October 2026, and it ate, no notes 🍓👑

📦 where this page comes from