ntb_default_port_number(9)

💅 ntb_default_port_number — like, the manual page, but make it make sense

Hey bestie 🫶 so this one is a kernel API page, manual section 9, and no cap it's a tiny little function that does exactly one thing. Let's get into it ✨

---

✨ NAME ✨

ntb_default_port_number — get the default local port number 💫

---

🎀 SYNOPSIS 🎀

int ntb_default_port_number (struct ntb_dev *ntb );

---

🦋 ARGUMENTS 🦋

• ntb — the NTB device context. That's it. That's the whole input, bestie 💜

---

🌸 DESCRIPTION 🌸

Okay so picture this: the hardware driver didn't specify a port_number callback method. Rude, but fine. In that case the NTB is considered to have just two ports — literally two, that's the whole vibe 💅 And so this method returns the default local port number in compliance with topology. Iconic, honestly.

NOTE 🚨 Don't call this method directly, bestie, I'm begging 😭 The ntb_port_number function should be used instead. Like, that's the main character — this one is just the understudy. Use the right one, periodt.

---

⭐ RETURN ⭐

the default local port number 👑

---

🌈 SEE ALSO 🌈

Kernel file ./include/linux/ntb.h — and then, um, the entire extended friend group of NTB symbols, iykyk: 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_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_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) 🫶

---

💖 okay that's the whole page, go read ntb_port_number(9) now like I told you 💖

anyway bestie, this one came from the kernel source over in ./include/linux and it's dated October 2026 — so like, remember it's the October 2026 era version, mwah 💋🎀 see u in the next manpage 🌸