On Mon, May 5, 2014 at 9:01 PM, Tejun Heo wrote:
> On Sun, Apr 27, 2014 at 12:08:56PM +0800, Lai Jiangshan wrote:
>> worker_idr is highly bound to managers and is always/only accessed in manager
>> lock context. So we don't need pool->lock for it.
>>
>> Signed-off-by: Lai Jiangshan
> ...
>> @@
On Mon, May 5, 2014 at 9:01 PM, Tejun Heo t...@kernel.org wrote:
On Sun, Apr 27, 2014 at 12:08:56PM +0800, Lai Jiangshan wrote:
worker_idr is highly bound to managers and is always/only accessed in manager
lock context. So we don't need pool-lock for it.
Signed-off-by: Lai Jiangshan
On Sun, Apr 27, 2014 at 12:08:56PM +0800, Lai Jiangshan wrote:
> worker_idr is highly bound to managers and is always/only accessed in manager
> lock context. So we don't need pool->lock for it.
>
> Signed-off-by: Lai Jiangshan
...
> @@ -378,14 +367,14 @@ static void copy_workqueue_attrs(struct
On Sun, Apr 27, 2014 at 12:08:56PM +0800, Lai Jiangshan wrote:
worker_idr is highly bound to managers and is always/only accessed in manager
lock context. So we don't need pool-lock for it.
Signed-off-by: Lai Jiangshan la...@cn.fujitsu.com
...
@@ -378,14 +367,14 @@ static void
worker_idr is highly bound to managers and is always/only accessed in manager
lock context. So we don't need pool->lock for it.
Signed-off-by: Lai Jiangshan
---
kernel/workqueue.c | 34 ++
1 files changed, 6 insertions(+), 28 deletions(-)
diff --git
worker_idr is highly bound to managers and is always/only accessed in manager
lock context. So we don't need pool-lock for it.
Signed-off-by: Lai Jiangshan la...@cn.fujitsu.com
---
kernel/workqueue.c | 34 ++
1 files changed, 6 insertions(+), 28 deletions(-)
6 matches
Mail list logo