ntb_default_peer_port_count(9)
π ntb_default_peer_port_count β Kernel API Manual β¨
okay so bestie, you know how every friend group has that one person who's like "how many people are we even inviting" and the answer is always, always one? Yeah. This is the kernel function that asks that question. Sit down, we're learning ntb_default_peer_port_count(9) from the Kernel API Manual, and honestly it's giving short-and-sweet main character energy π
πΈ NAME πΈ
ntb_default_peer_port_count β get the default number of peer device ports
likeβ¦ the baseline count. the factory setting. the "no customisation yet" answer πββοΈ
β¨ SYNOPSIS β¨
int ntb_default_peer_port_count (struct ntb_dev *ntb );
yeah that's it. that's the whole vibe. one argument, one int out, periodt π
π¦ ARGUMENTS π¦
ntbβ NTB device context. your little device buddy, handed over so the function knows who we're talking about π«Ά
π DESCRIPTION π
So here's the tea, bestie: by default hardware driver supports just one peer device. one. a single little buddy. that's the default, no cap π§
β οΈ NOTE β Don't call this method directly, fr fr. The ntb_peer_port_count function should be used instead. this one is like the backstage pass, not the front door π
π RETURN π
returns the default number of peer ports π«
(spoiler: per the description above, that default is one peer device. the function just tells you that, iconically.)
π₯ SEE ALSO π₯
Kernel file ./include/linux/ntb.h
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_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)
like, the entire NTB extended universe is in there. read it and weep (affectionately) ππ
that's the whole page bestie, you ate that ππ β sourced from ./include/linux, dated October 2026, page ntb_default_peer_port_count(9). mwah, go touch some kernel headers π
π¦ 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