bnx2i_send_iscsi_nopout(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… bnx2i_send_iscsi_nopout(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual β€” this is the page for bnx2i_send_iscsi_nopout, and honestly? it's a whole little baddie. let's get into it πŸŽ€


✨ NAME ✨

bnx2i_send_iscsi_nopout β€” post an iSCSI NOPOUT request WQE to the hardware, no cap πŸ’…


🌸 SYNOPSIS 🌸

int bnx2i_send_iscsi_nopout (struct bnx2i_conn *bnx2i_conn , struct
       iscsi_task *task , char *datap , int data_len , int unsol );

like, five args, returns an int, she's got range 🫢


πŸ¦‹ ARGUMENTS πŸ¦‹

  • bnx2i_conn β€” the iscsi connection, periodt. that's her whole thing.
  • task β€” the transport layer's command structure pointer, and she's the one requesting a WQE to get sent to the chip for further processing. main character energy fr.
  • datap β€” payload buffer pointer, i.e. the goods πŸ“¦
  • data_len β€” payload data length. how much goods.
  • unsol β€” this one indicates whether the nopout pdu is an unsolicited pdu, or if it's in response to the target's NOPIN w/ TTT != FFFFFFFF. literally the vibe check of the whole call ngl.

πŸ’œ DESCRIPTION πŸ’œ

prepare and post a nopout request WQE to the CNIC firmware ✨ that's it. that's the whole flex. she prepares it, she posts it, she leaves. iconic behavior honestly πŸ”₯


πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./drivers/scsi/bnx2i/bnx2i_hwi.c β€” and like, the whole extended family, because bnx2i functions travel in a pack πŸΊπŸ’•

like, yes, that's fifty-four cross-references and yes she knows every single one of them by name πŸ’€πŸ’–


that's the whole page bestie, iykyk 🌈

kisses and later, from the ./drivers/scsi/bnx2i girlies β€” this was documented in October 2026, and the page you just read was bnx2i_send_iscsi_nopout(9), signing off πŸŽ€βœ¨πŸ¦‹

πŸ“¦ where this page comes from