ntb_set_ctx(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… ntb_set_ctx(9) πŸ’…

okay so bestie, welcome to the Kernel API Manual page for ntb_set_ctx β€” she's a lil function but she's important, so pay attention πŸŽ€


✨ NAME ✨

ntb_set_ctx β€” the way you associate a driver context with an ntb device 🫢


🌸 SYNOPSIS 🌸

int ntb_set_ctx (struct ntb_dev *ntb , void *ctx , const struct
ntb_ctx_ops *ctx_ops );

πŸ¦‹ ARGUMENTS πŸ¦‹

  • ntb β€” the NTB device context. like, the actual device you're working with, mwah πŸ’–
  • ctx β€” the driver context. your stuff, your vibes.
  • ctx_ops β€” the driver context operations. the functions that go with it ✨

πŸ’œ DESCRIPTION πŸ’œ

So what she does is literally this: she associates a driver context and its operations with an ntb device. The context comes from the client driver, and no cap β€” the driver is allowed to associate a different context with each ntb device. Lowkey flexible. Iconic. πŸ’…


🌈 RETURN 🌈

Zero if the context is associated. Otherwise you get an error number 😭 (not the slay outcome, but ok, it happens).


πŸ‘‘ SEE ALSO πŸ‘‘

okay this list is LONG, like a full group chat roster, but every single one of them is here, fr fr 🫢

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_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_peer_msg_write(9), ntb_get_dma_dev(9), ntb_peer_resource_idx(9), ntb_peer_highest_mw_idx(9)


anyway that's the whole page bestie, go forth and associate those contexts πŸ’–βœ¨πŸŽ€

sign-off szn 🌸 β€” this one lives in ./include/linux and it's dated October 2026, so like, future vibes only β­πŸ’œ

πŸ“¦ where this page comes from