Login
You're viewing the functional.cafe public feed.
  • Nov 16, 2026, 6:33 PM

    ... allocates numerous work-queues, & propagates any failures.

    For each CPU-core it iterates over the BH & CPU worker pools. For each BH worker pool per CPU core it invokes a helper & another in turn to populates various properties & allocates (via radix-tree) an ID. Then it sets a flag, increments a counter, & prepares a callback for the IRQ-dispatch system.

    For each CPU worker pool per CPU core it invokes a similar initializer.

    2/3?

    💬 1🔄 1⭐ 0

Replies

  • Nov 16, 2026, 6:41 PM

    For each standard worker pool Linux allocates a workqueue-attrs object (via an initializer wrapped in a macro adding callbacks) with its CPU-mask vars, sets a `nice` attribute on those attrs & loads it into an array, & does so again for another array this time also setting an `ordered` flag.

    To allocate a workqueue it (via wrappers callbacks, variadic args, & lock properties) it validates flags, calculates how much memory's needed in one of 2 ways, allocates it, allocates attributes, ...

    3/3.2

    💬 1🔄 1⭐ 0
  • Nov 16, 2026, 6:48 PM

    ... formats a name, computes some limits to remember, sets various properties, inits a couple locks, inits some linkedlists, possibly allocates a worklist-node with their locks & linkedlists, under lock allocates (via a helper) much more data including attributes, under further locks recomputes (via a helper) the limits, adds the worklist to a linkedlist & creates (via another helper) a rescuer thread before releasing that lock, & registers a devfile with sysfs via another helper.

    4/4Fin today!

    💬 0🔄 1⭐ 0