diff options
| author |   Lai Jiangshan <laijs@cn.fujitsu.com> | 2014-05-22 19:01:16 +0800 |
|---|---|---|
| committer |   Tejun Heo <tj@kernel.org> | 2014-05-22 11:35:51 -0400 |
| commit | 74b414ead1133972817d3ce7b934356150d03a7d (patch) | |
| tree | 8942db6fda58c213804b66f8825fd736366b1597 /tools/perf/scripts/python/syscall-counts-by-pid.py | |
| parent | workqueue: rename first_worker() to first_idle_worker() (diff) | |
| download | wireguard-linux-74b414ead1133972817d3ce7b934356150d03a7d.tar.xz wireguard-linux-74b414ead1133972817d3ce7b934356150d03a7d.zip | |
workqueue: remove the confusing POOL_FREEZING
Currently, the global freezing state is propagated to worker_pools via
POOL_FREEZING and then to each workqueue; however, the middle step -
propagation through worker_pools - can be skipped as long as one or
more max_active adjustments happens for each workqueue after the
update to the global state is visible. The global workqueue freezing
state and the max_active adjustments during workqueue creation and
[un]freezing are serialized with wq_pool_mutex, so it's trivial to
guarantee that max_actives stay in sync with global freezing state.
POOL_FREEZING is unnecessary and makes the code more confusing and
complicates freeze_workqueues_begin() and thaw_workqueues() by
requiring them to walk through all pools.
Remove POOL_FREEZING and use workqueue_freezing directly instead.
tj: Description and comment updates.
Signed-off-by: Lai Jiangshan <laijs@cn.fujitsu.com>
Signed-off-by: Tejun Heo <tj@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/syscall-counts-by-pid.py')
0 files changed, 0 insertions, 0 deletions