diff options
| author | Tejun Heo <tj@kernel.org> | 2013-03-12 22:30:00 +0400 |
|---|---|---|
| committer | Tejun Heo <tj@kernel.org> | 2013-03-12 22:30:00 +0400 |
| commit | 34a06bd6b6fa92ccd9d3e6866b6cb91264c3cd20 (patch) | |
| tree | 546c715508dd2d4a80c754b24e41e1d4d2899775 /tools/perf/scripts/python/syscall-counts.py | |
| parent | fa1b54e69bc6c04674c9bb96a6cfa8b2c9f44771 (diff) | |
| download | linux-34a06bd6b6fa92ccd9d3e6866b6cb91264c3cd20.tar.xz | |
workqueue: replace POOL_MANAGING_WORKERS flag with worker_pool->manager_arb
POOL_MANAGING_WORKERS is used to synchronize the manager role.
Synchronizing among workers doesn't need blocking and that's why it's
implemented as a flag.
It got converted to a mutex a while back to add blocking wait from CPU
hotplug path - 6037315269 ("workqueue: use mutex for global_cwq
manager exclusion"). Later it turned out that synchronization among
workers and cpu hotplug need to be done separately. Eventually,
POOL_MANAGING_WORKERS is restored and workqueue->manager_mutex got
morphed into workqueue->assoc_mutex - 552a37e936 ("workqueue: restore
POOL_MANAGING_WORKERS") and b2eb83d123 ("workqueue: rename
manager_mutex to assoc_mutex").
Now, we're gonna need to be able to lock out managers from
destroy_workqueue() to support multiple unbound pools with custom
attributes making it again necessary to be able to block on the
manager role. This patch replaces POOL_MANAGING_WORKERS with
worker_pool->manager_arb.
This patch doesn't introduce any behavior changes.
v2: s/manager_mutex/manager_arb/
Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts.py')
0 files changed, 0 insertions, 0 deletions
