bnx2i_send_f...csi_init_msg(9)

💖 bnx2i_send_fw_iscsi_init_msg(9) — Kernel API Manual 💖

okay so bestie, welcome to the tea ☕ — this is the page for bnx2i_send_fw_iscsi_init_msg, and it lives in the Kernel API Manual, section 9. it's giving low-level driver lore and honestly? kinda iconic. let's get into it 🫶

---

✨ NAME ✨

bnx2i_send_fw_iscsi_init_msg — kicks off the very first handshake with the iscsi f/w, no cap 🤝

---

🌸 SYNOPSIS 🌸

int bnx2i_send_fw_iscsi_init_msg (struct bnx2i_hba *hba );

one function, one argument, one job. we love a simple signature 💅

---

🎀 ARGUMENTS 🎀

• hba — a pointer to the adapter structure. that's the whole thing. she just needs her adapter bestie and she's good to go 🦋

---

🧚 DESCRIPTION 🧚

so what's actually happening here? you send down the iscsi_init KWQEs, and that is what initiates the initial handshake with the f/w. it's the opening move, the "hey girl hey" of the whole operation 💌

this handshake is a whole moment, and here's what it brings you:

• iSCSi support validation — somebody has to confirm this is actually a thing we do, and that somebody is this call ✨
• on-chip context manager initialization — the context manager gets woken up and gets its life together 🧠

here's the timeline, because the drama has structure: the firmware completes this handshake with a CQE that's carrying the result of the iSCSi support validation. so yes, there's a whole CQE eventually showing up to spill the result 👀

and the parameter carried by the iscsi init request is doing double duty, bestie — it determines:

• the number of offloaded connection that this hba/chip can support 🎀
• the tolerance level for iscsi protocol violation that this hba/chip can support 🛡️

so like... that parameter is literally deciding how much chaos the chip is willing to put up with. respect 💀

---

👑 SEE ALSO 👑

kernel file: ./drivers/scsi/bnx2i/bnx2i_hwi.c — go read it, iykyk 📖

and the whole friend group (yes, all of them, i'm not skipping anyone, that's not the vibe):

• bnx2i_get_cid_num(9)
• bnx2i_adjust_qp_size(9)
• bnx2i_get_link_state(9)
• bnx2i_iscsi_license_error(9)
• bnx2i_arm_cq_event_coalescing(9)
• bnx2i_get_rq_buf(9)
• bnx2i_put_rq_buf(9)
• bnx2i_ring_sq_dbell(9)
• bnx2i_ring_dbell_update_sq_params(9)
• bnx2i_send_iscsi_login(9)
• bnx2i_send_iscsi_tmf(9)
• bnx2i_send_iscsi_text(9)
• bnx2i_send_iscsi_scsicmd(9)
• bnx2i_send_iscsi_nopout(9)
• bnx2i_send_iscsi_logout(9)
• bnx2i_update_iscsi_conn(9)
• bnx2i_ep_ofld_timer(9)
• bnx2i_send_cmd_cleanup_req(9)
• bnx2i_send_conn_destroy(9)
• bnx2i_570x_send_conn_ofld_req(9)
• bnx2i_5771x_send_conn_ofld_req(9)
• bnx2i_send_conn_ofld_req(9)
• setup_qp_page_tables(9)
• bnx2i_alloc_qp_resc(9)
• bnx2i_free_qp_resc(9)
• bnx2i_process_scsi_cmd_resp(9)
• bnx2i_process_login_resp(9)
• bnx2i_process_text_resp(9)
• bnx2i_process_tmf_resp(9)
• bnx2i_process_logout_resp(9)
• bnx2i_process_nopin_local_cmpl(9)
• bnx2i_unsol_pdu_adjust_rq(9)
• bnx2i_process_nopin_mesg(9)
• bnx2i_process_async_mesg(9)
• bnx2i_process_reject_mesg(9)
• bnx2i_process_cmd_cleanup_resp(9)
• bnx2i_percpu_io_thread(9)
• bnx2i_queue_scsi_cmd_resp(9)
• bnx2i_process_new_cqes(9)
• bnx2i_fastpath_notification(9)
• bnx2i_process_update_conn_cmpl(9)
• bnx2i_recovery_que_add_conn(9)
• bnx2i_process_tcp_error(9)
• bnx2i_process_iscsi_error(9)
• bnx2i_process_conn_destroy_cmpl(9)
• bnx2i_process_ofld_cmpl(9)
• bnx2i_indicate_kcqe(9)
• bnx2i_indicate_netevent(9)
• bnx2i_cm_connect_cmpl(9)
• bnx2i_cm_close_cmpl(9)
• bnx2i_cm_abort_cmpl(9)
• bnx2i_cm_remote_close(9)
• bnx2i_cm_remote_abort(9)
• bnx2i_map_ep_dbell_regs(9)

like i said. the whole group chat. 💜

---

kay so that's the page, bestie 🎀 this lil drop came from ./drivers/scsi/bnx2i, dated October 2026, and it's filed under bnx2i_send_f...csi_init_msg(9) — yes that's the abbreviated title, yes it's a whole mood, we don't question the truncation 💅✨