ib_cm_notify(9)

📦 version 7.3.1, in nixpkgs unstable

✨ ib_cm_notify ✨

okay so bestie, welcome to ib_cm_notify(9) from the Kernel API Manual 🎀 — this is the little function that tells the CM (that's the Connection Manager, iykyk) that something happened, so the CM isn't just sitting there like 💀

🌸 SYNOPSIS 🌸

int ib_cm_notify (struct ib_cm_id *cm_id , enum ib_event_type event );

it returns int, it takes two args, and it is literally not that deep — you pass in the connection and the event, bestie.

🦋 ARGUMENTS 🦋

  • cm_id — the connection identifier to transition to established 👑 this is the one getting its glow-up into the established state.
  • event — the type of event. that's it. that's the arg. what kind of event, you ask? keep reading, babe 💅

💖 DESCRIPTION 💖

so the way this works: you — yes you, the user — are supposed to call this routine to notify the CM about relevant communication events 🫶. It's giving "please keep the CM in the loop, it hates being left on read" energy.

The events that should be reported to the CM, and when to report them, are:

  • IB_EVENT_COMM_EST — used when a message is received on a connected QP before an RTU has been received 🌈. like, hello?? we're not even at RTU yet and a message is already here, so somebody's gotta tell the CM.
  • IB_EVENT_PATH_MIG — notifies the CM that the connection has failed over to the alternate path 🔥. the connection said "not this path, that one" and the CM needs to know, fr fr.
no cap, those are the only two events listed here. don't go inventing more, bestie 💀

🧚 SEE ALSO 🧚

Kernel file ./include/rdma/ib_cm.h — and bestie, it's a whole friend group of CM functions, look at this roster 👑

mwah 💋 that's the whole page. sourced from ./include/rdma, dated October 2026, and filed under ib_cm_notify(9) — go notify your CM, bestie, it's been waiting 🌸✨

📦 where this page comes from