ntb_msg_outbits(9)
πΈ ntb_msg_outbits (9) β Kernel API Manual energy π
okay so bestie, welcome to the Kernel API Manual, section 9, where we learn about one (1) tiny function that tells you a whole lot about your outbound message registers. she's small, she's specific, she slays. let's go π
β¨ NAME β¨
ntb_msg_outbits β get a bitfield of outbound message registers status. that's it, that's her whole job, and she does it beautifully π«Ά
β¨ SYNOPSIS β¨
u64 ntb_msg_outbits (struct ntb_dev *ntb );
literally one argument, one return value, zero drama. iconic behavior ngl β
β¨ ARGUMENTS β¨
ntbβ the NTB device context. your device, your vibe, your context. you hand her thestruct ntb_dev *and she does the rest π
β¨ DESCRIPTION β¨
so the way this works: the method returns the bitfield of status and mask registers, which related to outbound message registers. yes bestie, a whole bitfield β every bit is a little status flag doing its own thing, masked and matching, all bundled up in one u64 like a cute little gift box π
it's giving "I asked for the outbound message register situation and got a whole bitmap back." no cap. and honestly? we love a function that knows exactly what it is π₯
β¨ RETURN β¨
the bitfield of outbound message registers. that's the whole return value. one u64, all the bits, done. periodt π
β¨ SEE ALSO β¨
the entire extended universe, fr fr. read these next if you wanna be a real NTB main character π
The enums and structs (the lore) π
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)
Client & device registration π§
Context & events π¦
Ports (so many ports) πΈ
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_logical_port_number(9),ntb_peer_port_idx(9)
Links π
Memory windows β¨
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)
Doorbells π
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)
Scratchpads π
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)
Messages (her home turf, where our girl lives) π
ntb_msg_count(9),ntb_msg_inbits(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)
The stragglers, but make them fancy π
lowkey that's the wholeinclude/linux/ntb.hfriend group. go readntb_msg_inbits(9)next, she's literally the inbound mirror of this one. matching set π«Ά
and that's the page bestie! it lives in ./include/linux and this version is dated October 2026 β so yeah, fresh off the press, go forth and read your bitfields πβ¨π
π¦ 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