ntb_peer_db_clear_mask(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

okay bestie, welcome to the ntb_peer_db_clear_mask(9) page in the Kernel API Manual β€” group-chat edition ✨

🌸 NAME 🌸

ntb_peer_db_clear_mask β€” clear bits in the peer doorbell mask

✨ SYNOPSIS ✨

int ntb_peer_db_clear_mask (struct ntb_dev *ntb , u64 db_bits );

πŸŽ€ ARGUMENTS πŸŽ€

  • ntb β€” NTB device context. The device context you're working with, bestie.
  • db_bits β€” Doorbell bits to clear. The doorbell bits that are getting cleared.

πŸ¦‹ DESCRIPTION πŸ¦‹

Clear bits in the peer doorbell mask register, allowing doorbell interrupts from being generated for those doorbell bits. That's the whole vibe: clear those mask bits, let the doorbell interrupts happen for them πŸ’…

🚨 okay but fr fr: if the hardware does not generate the interrupt on clearing the mask bit, then the driver should not implement this function! Like, do not pass go, do not collect any doorbell interrupts.

This is unusual, and hardware may not support it. No cap β€” the man page literally says so 😭

πŸ”₯ RETURN πŸ”₯

Zero on success, otherwise an error number. Slay when it's zero; error number when it's not ✨

🌈 SEE ALSO 🌈

Kernel file: ./include/linux/ntb.h

The whole reference squad, in order: 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_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)


that's the whole page, bestie 🫢 source/version: ./include/linux Β· date: October 2026 Β· manual page: ntb_peer_db_clear_mask(9) πŸ’–

πŸ“¦ where this page comes from