ntb_peer_msg_write(9)
β¨ NAME β¨
okay bestie, this is ntb_peer_msg_write(9) from the Kernel API Manual β the function that writes data to the specified peer message register. That's the whole vibe: peer message register, data goes in, main character energy only π
.
πΈ SYNOPSIS πΈ
int ntb_peer_msg_write (struct ntb_dev *ntb , int pidx , int midx , u32
msg );
that's the signature, no cap β¨.
π ARGUMENTS π
ntbβ NTB device context. Like, the device bestie you're working with.pidxβ Port index of peer device a message being sent to.midxβ Message register index.msgβ Data to send. The actual data, the star of the show π.
π DESCRIPTION π
Send data to a specified peer device using the defined message register. Message event can be raised if the midx registers isn't empty while calling this method and the corresponding interrupt isn't masked.
that's the exact lore drop, bestie β don't skip it π.
β RETURN β
Zero on success, otherwise a negative error number.
so 0 is the slay result, and anything negative is the "bestie something went wrong" number π«Ά.
π SEE ALSO π
Kernel file: ./include/linux/ntb.h β this is the mothership file, and here's the whole friend group, fr fr:
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_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_get_dma_dev(9)ntb_peer_resource_idx(9)ntb_peer_highest_mw_idx(9)
mwah π the source/version footer says ./include/linux, dated October 2026, manual name ntb_peer_msg_write(9) β that's the whole footer, bestie, now go write some peer messages π«Άπ.
π¦ 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