bnx2i_conn_bind(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… bnx2i_conn_bind(9) β€” the Kernel API Manual glow-up πŸ’…

okay so bestie, this is bnx2i_conn_bind(9) from the Kernel API Manual, and it’s giving β€œglue three things together and hope the TCP connection behaves” energy. Let’s get into it. ✨

🌸 NAME 🌸

bnx2i_conn_bind β€” binds iscsi sess, conn and ep objects together. That’s the whole assignment, no cap. 🫢

✨ SYNOPSIS ✨

int bnx2i_conn_bind (struct iscsi_cls_session *cls_session , struct
       iscsi_cls_conn *cls_conn , uint64_t transport_fd , int is_leading );

πŸŽ€ ARGUMENTS πŸŽ€

  • cls_session β€” pointer to iscsi cls session. It’s the session-side bestie. πŸ’–
  • cls_conn β€” pointer to iscsi cls conn. The connection-side bestie.
  • transport_fd β€” 64-bit EP handle. Yes, 64-bit. Big handle energy. πŸ”₯
  • is_leading β€” leading connection on this session? Basically: is this the main-character connection? πŸ‘‘

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so what it does: it binds together the iSCSI session instance, the iSCSI connection instance, and the TCP connection. Three-way friendship bracelet, but for kernel objects. πŸ’…

This routine returns an error code if the TCP connection does not belong on the device where the iSCSI sess/conn is bound. So yeah, if the TCP connection is at the wrong party, it’s not slaying, and you get an error code. 😭

🌈 SEE ALSO 🌈

Kernel file ./drivers/scsi/bnx2i/bnx2i_iscsi.c β€” yes, that exact path. 🫢

The whole SEE ALSO squad, no skips, no cap:


Sign-off vibes: source/version is ./drivers/scsi/bnx2i, and the date is October 2026. Periodt. πŸ’‹βœ¨

πŸ“¦ where this page comes from