ntb_db_set_mask(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ntb_db_set_mask(9) β€” like, the Kernel API Manual page, bestie ✨

Okay so we're in the ntb_db_set_mask(9) corner of the Kernel API Manual, and honestly? This one is a little baddie. Let's get into it πŸŽ€


✨ NAME ✨

ntb_db_set_mask β€” set bits in the local doorbell mask πŸ””


🌸 SYNOPSIS 🌸

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

πŸ¦‹ ARGUMENTS πŸ¦‹

  • ntb β€” the NTB device context. Like, the device we're doing this to πŸ’œ
  • db_bits β€” the doorbell mask bits you wanna set. These exact ones. No cap 🫢

πŸ’– DESCRIPTION πŸ’–

So what this does is set bits in the local doorbell mask register, which stops doorbell interrupts from being generated for those doorbell bits. The way that works is literally it's masking them out β€” no interrupt for you, bestie πŸ™ˆ

And the important part, the part you do not skip: bits that were already set must remain set. That's the whole vibe check. Don't be out here clearing bits you weren't asked to touch, periodt πŸ’…


⭐ RETURN ⭐

Zero on success πŸŽ‰ otherwise an error number 😭


πŸ‘‘ SEE ALSO πŸ‘‘

Kernel file ./include/linux/ntb.h, plus the whole extended friend group:

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_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)


ngl bestie, that SEE ALSO list is giving "everyone showed up to the party" energy πŸ”₯ read the whole thing, iykyk

Okay that's the page!! Signing off from ./include/linux, dated October 2026 β€” stay masked, stay iconic, mwah πŸ’‹πŸŽ€πŸ¦‹

πŸ“¦ where this page comes from