On Thu, Oct 30, 2025 at 6:15 PM Christian König <[email protected]> wrote: >[...] > Adding Philip and Felix to comment, but this should most likely also not > execute on the same CPU as the one who scheduled the work.
Hi Christian, The actual behavior without WQ_PERCPU is exactly the same: with 0 it means the workqueue is per-cpu. We just enforced that, adding the WQ_PERCPU flag, so that it is explicit. So if you need this to be unbound, I can send the v2 with WQ_UNBOUND instead of WQ_PERCPU. Thanks! -- Marco Crivellari L3 Support Engineer, Technology & Product
