ntb_peer_log..._port_number(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ NAME ✨

okay bestie, welcome to the Kernel API Manual page for ntb_peer_logical_port_number β€” the one and only ntb_peer_log..._port_number(9) (yes, the title up top gets a lil truncated moment, iykyk πŸ’…). She's here to get the logical peer port by given index. Periodt.

🌸 SYNOPSIS 🌸

int ntb_peer_logical_port_number (struct ntb_dev *ntb , int pidx );

πŸŽ€ ARGUMENTS πŸŽ€

  • ntb β€” NTB device context. That's the main-character device you're working with, bestie.
  • pidx β€” Peer port index. The index you're asking about.

πŸ¦‹ DESCRIPTION πŸ¦‹

Okay so the Logical Port Number is defined to be a unique number for each port, starting from zero through to the number of ports minus one. Literally the group-chat numbering system: 0, 1, 2, … and so on until ports-minus-one.

This is in contrast to the Port Number, where each port can be assigned any unique physical number by the hardware. So logical = the cute sequential ID; physical = whatever number the hardware decided to hand out.

The logical port number is useful for calculating the resource indexes used by peers. That's the whole reason she exists, no cap.

πŸ’… RETURN πŸ’…

She returns the peer's logical port number or a negative value indicating an error. If you see negative, that's your signal that something went sideways β€” not a vibe. πŸ’€

πŸ‘‘ SEE ALSO πŸ‘‘

The kernel file ./include/linux/ntb.h is the home base, and the whole friend group is: enum ntb_topo(9), enum ntb_speed(9), enum ntb_width(9), enum ntb_default_port(9), struct ntb_client_ops(9), struct ntb_ctx_ops(9), struct ntb_dev_ops(9), struct ntb_client(9), struct ntb_dev(9), ntb_register_client(9), ntb_unregister_client(9), ntb_register_device(9), ntb_unregister_device(9), ntb_set_ctx(9), ntb_clear_ctx(9), ntb_link_event(9), ntb_db_event(9), ntb_msg_event(9), ntb_default_port_number(9), ntb_default_peer_port_count(9), ntb_default_peer_port_number(9), ntb_default_peer_port_idx(9), ntb_port_number(9), ntb_peer_port_count(9), ntb_peer_port_number(9), ntb_logical_port_number(9), ntb_peer_port_idx(9), ntb_link_is_up(9), ntb_link_enable(9), ntb_link_disable(9), ntb_mw_count(9), ntb_mw_get_align(9), ntb_mw_set_trans(9), ntb_mw_clear_trans(9), ntb_peer_mw_count(9), ntb_peer_mw_get_addr(9), ntb_peer_mw_set_trans(9), ntb_peer_mw_clear_trans(9), ntb_db_is_unsafe(9), ntb_db_valid_mask(9), ntb_db_vector_count(9), ntb_db_vector_mask(9), ntb_db_read(9), ntb_db_set(9), ntb_db_clear(9), ntb_db_read_mask(9), ntb_db_set_mask(9), ntb_db_clear_mask(9), ntb_peer_db_addr(9), ntb_peer_db_read(9), ntb_peer_db_set(9), ntb_peer_db_clear(9), ntb_peer_db_read_mask(9), ntb_peer_db_set_mask(9), ntb_peer_db_clear_mask(9), ntb_spad_is_unsafe(9), ntb_spad_count(9), ntb_spad_read(9), ntb_spad_write(9), ntb_peer_spad_addr(9), ntb_peer_spad_read(9), ntb_peer_spad_write(9), ntb_msg_count(9), ntb_msg_inbits(9), ntb_msg_outbits(9), ntb_msg_read_sts(9), ntb_msg_clear_sts(9), ntb_msg_set_mask(9), ntb_msg_clear_mask(9), ntb_msg_read(9), ntb_peer_msg_write(9), ntb_get_dma_dev(9), ntb_peer_resource_idx(9), ntb_peer_highest_mw_idx(9).


mwah πŸ’– that's the whole page, bestie. Source/version: ./include/linux; date: October 2026; manual name: ntb_peer_log..._port_number(9). Go slay those logical ports πŸ‘‘βœ¨

πŸ“¦ where this page comes from