bnx2i_check_route(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… bnx2i_check_route(9) β€” a Kernel API Manual moment

ok so bestie, welcome to the little corner of the kernel API manual all about bnx2i_check_route, part of the bnx2i fam. it's a tiny little function but it's doing important work, and we're gonna get into it. no cap. πŸ¦‹


✨ NAME ✨

bnx2i_check_route β€” checks if the target IP route belongs to one of the NX2 devices πŸŽ€

like, is this route ours? is it in the family? that's the whole vibe check. 🫢


🌸 SYNOPSIS 🌸

struct bnx2i_hba * bnx2i_check_route (struct sockaddr *dst_addr );

that's it. that's the whole call. hand it one address and it hands you back a struct bnx2i_hba *. giving very much "you give me a vibe, I give you a hardware control block." πŸ’…


⭐ ARGUMENTS ⭐

  • dst_addr β€” the target IP address, aka the thing you're asking about. drop it in and let the function decide if it belongs to a BNX2 device. πŸ“

πŸ‘‘ DESCRIPTION πŸ‘‘

check if the route resolves to a BNX2 device. πŸ”₯

that's literally it, that's the whole job β€” it looks at the route and goes "okay, does this resolve to a BNX2 device or not?" and answers accordingly. lowkey iconic how simple it is. πŸ’œ


🌈 SEE ALSO 🌈

the source lives right here in the kernel file ./drivers/scsi/bnx2i/bnx2i_iscsi.c β€” go read it bestie, it's all in there. 🧚

and now, the shoutouts. the whole squad, in order, no one left out, periodt: bnx2i_get_write_cmd_bd_idx(9), bnx2i_setup_write_cmd_bd_info(9), bnx2i_map_scsi_sg(9), bnx2i_iscsi_map_sg_list(9), bnx2i_iscsi_unmap_sg_list(9), bnx2i_bind_conn_to_iscsi_cid(9), bnx2i_get_conn_from_id(9), bnx2i_alloc_iscsi_cid(9), bnx2i_free_iscsi_cid(9), bnx2i_setup_free_cid_que(9), bnx2i_release_free_cid_que(9), bnx2i_alloc_ep(9), bnx2i_free_ep(9), bnx2i_alloc_bdt(9), bnx2i_destroy_cmd_pool(9), bnx2i_setup_cmd_pool(9), bnx2i_setup_mp_bdt(9), bnx2i_free_mp_bdt(9), bnx2i_drop_session(9), bnx2i_ep_destroy_list_add(9), bnx2i_ep_destroy_list_del(9), bnx2i_ep_ofld_list_add(9), bnx2i_ep_ofld_list_del(9), bnx2i_find_ep_in_ofld_list(9), bnx2i_find_ep_in_destroy_list(9), bnx2i_ep_active_list_add(9), bnx2i_ep_active_list_del(9), bnx2i_setup_host_queue_size(9), bnx2i_alloc_hba(9), bnx2i_free_hba(9), bnx2i_conn_free_login_resources(9), bnx2i_conn_alloc_login_resources(9), bnx2i_iscsi_prep_generic_pdu_bd(9), bnx2i_iscsi_send_generic_request(9), bnx2i_cpy_scsi_cdb(9), bnx2i_mtask_xmit(9), bnx2i_task_xmit(9), bnx2i_session_create(9), bnx2i_session_destroy(9), bnx2i_conn_create(9), bnx2i_conn_bind(9), bnx2i_conn_destroy(9), bnx2i_ep_get_param(9), bnx2i_host_get_param(9), bnx2i_conn_start(9), bnx2i_conn_get_stats(9), bnx2i_tear_down_conn(9), bnx2i_ep_connect(9), bnx2i_ep_poll(9), bnx2i_ep_tcp_conn_active(9), bnx2i_hw_ep_disconnect(9), bnx2i_ep_disconnect(9), bnx2i_nl_set_path(9). 😭 the way that's a whole friend group. iykyk. πŸ’–


ngl bestie this one's short and sweet β€” don't overthink it, just check the route and move on. ✨

alright that's the page!! mwah πŸ’‹ this whole thing came out of ./drivers/scsi/bnx2i, October 2026 edition β€” go off, read the source, slay your kernel debugging era. πŸŽ€πŸ¦‹πŸ’…

πŸ“¦ where this page comes from