blkcg_set_delay(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

πŸ’… blkcg_set_delay β€” the Kernel API Manual edition, bestie ✨

okay so real talk, this one's from the Kernel API Manual (section 9, kernel-functions energy), and it's lowkey a little diva function. let's get into it πŸŽ€


✨ NAME ✨

blkcg_set_delay β€” turns on the allocator delay mechanism with the exact delay amount you hand it. that's the whole gig. no cap 🫢


🌸 SYNOPSIS 🌸

void blkcg_set_delay (struct blkcg_gq *blkg , u64 delay );

like... that's it. void return, two args, she's simple and she knows it πŸ’…


πŸ¦‹ ARGUMENTS πŸ¦‹

  • blkg β€” the target blkg. the main character of this operation, fr fr πŸ‘‘
  • delay β€” the delay duration, measured in nsecs (nanoseconds, bestie, we're down to the nano level here ⏱️✨)

πŸ’œ DESCRIPTION πŸ’œ

so when you enable this thing with this function, hear me out: the delay is not decayed. like, it does not fade, it does not shrink, it does not gently let itself out β€” nothing. it just sits there 🌈

because of that, you have to explicitly clear it with blkcg_clear_delay. no auto-cleanup, no self-care, you gotta do the work yourself 😀

⚠️ also and this is the important part: Must not be mixed with blkcg_[un]use_delay and blkcg_add_delay usages. like do not. do not do that. the vibes will be rancid and it's giving undefined-behavior-adjacent chaos πŸ’€ keep your delay mechanisms in separate lanes, iykyk πŸ™ˆ

πŸ”₯ SEE ALSO πŸ”₯

the whole friend group, in order, exactly as listed:

like genuinely go read blkcg_clear_delay(9) next, she's literally the cleanup crew for this one πŸ§ΉπŸ’–


and that's the page, bestie!! sourced fresh from ./block, dated October 2026, filed under blkcg_set_delay(9) β€” slay, go touch some block cgroups, ily, bye πŸŽ€πŸ«Άβ­

πŸ“¦ where this page comes from