bnx2i_proces...te_conn_cmpl(9)
π NAME π
bnx2i_process_update_conn_cmpl β bestie, this is the one that handles the completion of an iscsi conn update. Yeah. That KCQE. π«Ά
So like, quick vibe check: this page lives in the Kernel API Manual (that's the manual name, in case anyone was wondering β¨), and it's about one specific function out of the whole bnx2i family. Let me put you on.
β¨ SYNOPSIS β¨
void bnx2i_process_update_conn_cmpl (struct bnx2i_hba *hba , struct
iscsi_kcqe *update_kcqe );
That's the whole signature, no cap. Returns void, so like... nothing comes back. It just does things. Iconic behavior honestly.
π ARGUMENTS π
hbaβ the adapter structure pointer π like, the actual HBA we're talking about. That's your main character.update_kcqeβ kcqe pointer. Yeah, just a pointer to the kcqe. Short and sweet, she doesn't need a whole paragraph.
π¦ DESCRIPTION π¦
Okay so this is the CONN_UPDATE completion handler. And what does it do, you ask? It completes iSCSI connection FFP migration. That's it. That's the whole job. It's giving "one task, done flawlessly." π₯
Like literally, that's the entire description β the conn update comes in, this handler catches it, FFP migration gets completed, we move on with our lives. Clean. Simple. Slay. π
ngl it's a short page, but not every function needs a novel. Some of them just show up, do their one job, and leave. Respect. π
π SEE ALSO π
Okay bestie, buckle up, because this list is LONG β it's the whole bnx2i friend group and they ALL showed up to the group chat ππ. The kernel file is ./drivers/scsi/bnx2i/bnx2i_hwi.c, and here's everyone:
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_send_fw_iscsi_init_msg(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_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)
Fifty-four entries. Fifty-four!! I counted. My fingers hurt. π But every single one is here, so nobody can come for me. Group chat fully accounted for. π«Ά
okay that's the whole page bestie, hope it ate π β¨
And before I go β cute little sign-off time π: this one comes from the source ./drivers/scsi/bnx2i, dated October 2026, and it's filed under the manual page title bnx2i_proces...te_conn_cmpl(9) (yes, still truncated with the dots, we don't make the rules, the header format does π). Bye bestie, go complete some FFP migrations! π¦π
π¦ where this page comes from
- nixpkgs unstable: linux-manual 7.3.1
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash-1017 on : a language model's rewrite of the original, under its terms