alloc_ordered_workqueue(9)

πŸ“¦ version 7.3.1, in nixpkgs unstable

✨ alloc_ordered_workqueue(9) ✨

okay so bestie, welcome to the alloc_ordered_workqueue page πŸ’… this is a Kernel API Manual entry and it's genuinely one of the cutest little allocation functions in the kernel, fr fr. buckle up πŸŽ€


🌸 NAME 🌸

alloc_ordered_workqueue β€” allocate an ordered workqueue 🌈


✨ SYNOPSIS ✨

alloc_ordered_workqueue (fmt , flags , args... );

like yes, that's the whole vibe 😌 three parameter slots, one dream.


πŸ¦‹ ARGUMENTS πŸ¦‹

  • fmt β€” the printf format for the name of the workqueue 🏷️ this is literally what your wq is gonna be called, so make it good
  • flags β€” the WQ_* flags πŸ’« and listen, only WQ_FREEZABLE and WQ_MEM_RECLAIM are actually meaningful here, the rest are just... there, doing nothing, no cap πŸ™ˆ
  • args β€” the args for fmt 🫢 you know, the stuff that fills in the format placeholders

πŸ’– DESCRIPTION πŸ’–

so what does it do? it allocates an ordered workqueue πŸ‘‘ An ordered workqueue executes at most one work item at any given time, and it does it in the queued order ⭐ like a very polite single-file line where nobody cuts 🧚

and how are they implemented, you ask? they're implemented as unbound workqueues with max_active of one πŸ”₯ that's the whole secret, iykyk.


πŸŽ€ RETURN πŸŽ€

  • Pointer to the allocated workqueue on success βœ…
  • NULL on failure 😭
check for that NULL, bestie, please πŸ™ it's giving "unhandled error" energy and we don't want that for you.

πŸ’œ SEE ALSO πŸ’œ

all the friends in the same friend group:


and that's the page, bestie 🫢 shoutout to the source tree at ./include/linux, dated October 2026, and to the manual page alloc_ordered_workqueue(9) itself β€” iconic, no notes πŸ’…βœ¨πŸ“

πŸ“¦ where this page comes from