dev_deactivate_many(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… dev_deactivate_many(9) β€” like, the Kernel API Manual one πŸŽ€

okay so bestie, buckle up, we're in the Kernel API Manual today and this one is lowkey important πŸ‘‘


✨ NAME ✨

dev_deactivate_many β€” deactivate transmissions on several devices πŸ¦‹

Like, several devices. Not one. Many. plural. the way that this function said "group project" and meant it πŸ’€


🌸 SYNOPSIS 🌸

void dev_deactivate_many (struct list_head *head , bool reset_needed );

that's literally it. two args. no cap, no hidden extras. she's simple, she's iconic 🫢


πŸŽ€ ARGUMENTS πŸŽ€

  • head β€” a list of devices to deactivate ✨ like the guest list, but for transmission shutdown πŸ’…
  • reset_needed β€” a bool, and if it's true, the qdisc should be reset πŸ”₯ yes bestie, the qdisc. reset her. if it's true, anyway. otherwise mind your business πŸ™ˆ

πŸ’– DESCRIPTION πŸ’–

okay so here's the vibe check: this function returns only when all outstanding transmissions have completed ⭐ like she will not leave the group chat until everyone's messages have been delivered, periodt.

BUT πŸ’€ β€” and this is the one caveat β€” that's unless all devices are in dismantle phase. if every single device is in dismantle phase, then nope, that guarantee does not apply. fr fr, read it again so you don't get caught out 😭

so yeah: outstanding transmissions completed β†’ she comes back. all devices in dismantle phase β†’ that's the exception, don't @ me 🌈


🧚 SEE ALSO 🧚


πŸ’… a tiny reminder from me to you: the head list goes in, and reset_needed is a plain old bool β€” true means reset the qdisc, and that's the whole assignment bestie ✨

πŸŽ€ and that's the page! brought to you by ./net/sched, dated October 2026, and yes she closes it out with dev_deactivate_many(9) like the queen she is. iykyk πŸ’–βœ¨πŸ¦‹

πŸ“¦ where this page comes from