diff options
author | Tejun Heo <tj@kernel.org> | 2023-08-08 04:57:23 +0300 |
---|---|---|
committer | Tejun Heo <tj@kernel.org> | 2023-08-08 04:57:23 +0300 |
commit | 687a9aa56f811b381e63f7f8f9149428ac708a3b (patch) | |
tree | 16d5b3fc2afffde2d9346cace39ce2116b2c1d90 /tools/perf/scripts/python/export-to-postgresql.py | |
parent | 967b494e2fd143a9c1a3201422aceadb5fa9fbfc (diff) | |
download | linux-687a9aa56f811b381e63f7f8f9149428ac708a3b.tar.xz |
workqueue: Make per-cpu pool_workqueues allocated and released like unbound ones
Currently, all per-cpu pwq's (pool_workqueue's) are allocated directly
through a per-cpu allocation and thus, unlike unbound workqueues, not
reference counted. This difference in lifetime management between the two
types is a bit confusing.
Unbound workqueues are currently accessed through wq->numa_pwq_tbl[] which
isn't suitiable for the planned CPU locality related improvements. The plan
is to unify pwq handling across per-cpu and unbound workqueues so that
they're always accessed through wq->cpu_pwq.
In preparation, this patch makes per-cpu pwq's to be allocated, reference
counted and released the same way as unbound pwq's. wq->cpu_pwq now holds
pointers to pwq's instead of containing them directly.
pwq_unbound_release_workfn() is renamed to pwq_release_workfn() as it's now
also used for per-cpu work items.
Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions