linux-kernel - Re: [PATCH v2 2/4] fs/afs/rxrpc: Remove deprecated create_singlethread

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:   Tue, 30 Aug 2016 23:15:43 +0100
From:   David Howells <dhowells@...hat.com>
To:     Bhaktipriya Shridhar <bhaktipriya96@...il.com>
Cc:     dhowells@...hat.com, linux-afs@...ts.infradead.org,
        linux-kernel@...r.kernel.org, Tejun Heo <tj@...nel.org>
Subject: Re: [PATCH v2 2/4] fs/afs/rxrpc: Remove deprecated create_singlethread_workqueue

Bhaktipriya Shridhar <bhaktipriya96@...il.com> wrote:

> The workqueue "afs_async_calls" queues a single work item viz
> &call->async_work and hence it doesn't require execution ordering.
> ...
> Since there are fixed number of work items, explicit concurrency
> limit is unnecessary here.

There can be more than one single call and there's no fixed number.

> The workqueue "afs_lock_manager" queues a single work item
> &vnode->lock_work, and hence it doesn't require execution ordering.
> ...
> Since there are fixed number of work items, explicit concurrency
> limit is unnecessary here.

There may be more than one single vnode and there's no fixed number.

David