mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Tejun Heo <tj@kernel.org>
To: David Howells <dhowells@redhat.com>
Cc: Bhaktipriya Shridhar <bhaktipriya96@gmail.com>,
	linux-afs@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/4] fs/afs/rxrpc: Remove deprecated create_singlethread_workqueue
Date: Wed, 31 Aug 2016 10:40:54 -0400	[thread overview]
Message-ID: <20160831144054.GW12660@htj.duckdns.org> (raw)
In-Reply-To: <26365.1472595343@warthog.procyon.org.uk>

On Tue, Aug 30, 2016 at 11:15:43PM +0100, David Howells wrote:
> Bhaktipriya Shridhar <bhaktipriya96@gmail.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.

Ah, okay, the work items are dynamically allocated.  Do they need
strict execution ordering or can they be executed concurrently?

Thanks.

-- 
tejun

  reply	other threads:[~2016-08-31 14:41 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <cover.1472589043.git.bhaktipriya96@gmail.com>
2016-08-30 20:32 ` [PATCH v2 1/4] fs/afs/vlocation: " Bhaktipriya Shridhar
2016-08-30 20:33 ` [PATCH v2 2/4] fs/afs/rxrpc: " Bhaktipriya Shridhar
2016-08-30 20:33 ` [PATCH v2 3/4] fs/afs/callback: " Bhaktipriya Shridhar
2016-08-30 20:34 ` [PATCH v2 4/4] fs/afs/flock: " Bhaktipriya Shridhar
2016-08-30 22:15 ` [PATCH v2 2/4] fs/afs/rxrpc: " David Howells
2016-08-31 14:40   ` Tejun Heo [this message]
2016-08-31 20:24   ` David Howells
2016-08-31 21:17     ` Tejun Heo
2016-09-01 13:45       ` Bhaktipriya Shridhar

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160831144054.GW12660@htj.duckdns.org \
    --to=tj@kernel.org \
    --cc=bhaktipriya96@gmail.com \
    --cc=dhowells@redhat.com \
    --cc=linux-afs@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®