ib_dispatch_event(9)
π ib_dispatch_event(9) β like, the kernel API manual bestie β¨
Okay so today we're learning about ib_dispatch_event, which lives in section 9 of the Kernel API Manual. Buckle up, it's literally a one-liner and yet somehow still iconic π
πΈ NAME πΈ
ib_dispatch_event β dispatch an asynchronous event. That's it, that's the whole vibe check π«
β¨ SYNOPSIS β¨
void ib_dispatch_event (const struct ib_event *event );
Short, sweet, returns nothing, takes one thing. Main character energy fr fr π
π«Ά ARGUMENTS π«Ά
eventβ the event you're dispatching. Yes bestie, that's the one. Hand it over π
π₯ DESCRIPTION π₯
Okay so listen up, low-level driver besties, this part is for you:
When an asynchronous event happens, low-level drivers must call ib_dispatch_event to dispatch that event to all registered event handlers. All of them. Not some, not one, not "whoever's around" β all the registered event handlers get it. That's the whole job π¦
Lowkey simple, highkey important β "must call" is not a suggestion, bestie π
π SEE ALSO π
Everything else in the friend group π:
- Kernel file
./drivers/infiniband/core/cache.cfree_gid_work(9) del_gid(9)add_modify_gid(9)rdma_find_gid_by_port(9)rdma_find_gid_by_filter(9)rdma_query_gid(9)rdma_read_gid_hw_context(9)rdma_find_gid(9)rdma_get_gid_attr(9)rdma_query_gid_table(9)rdma_put_gid_attr(9)rdma_hold_gid_attr(9)rdma_read_gid_attr_ndev_rcu(9)rdma_read_gid_l2_fields(9)
And that's the tea β from ./drivers/infiniband/core, dated October 2026 β this page said ib_dispatch_event(9) at the top and it's saying it again down here, periodt π
β¨
π¦ 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