From: Christoph Hellwig <hch@infradead.org>
To: NeilBrown <neilb@suse.de>
Cc: Trond Myklebust <trond.myklebust@primarydata.com>,
NFS <linux-nfs@vger.kernel.org>, Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH/RFC] NFS: state manager thread must start running.
Date: Tue, 15 Jul 2014 00:49:42 -0700 [thread overview]
Message-ID: <20140715074942.GA6166@infradead.org> (raw)
In-Reply-To: <20140715163942.1d94304f@notabene.brown>
On Tue, Jul 15, 2014 at 04:39:42PM +1000, NeilBrown wrote:
> I suggested in an earlier email that it might be possible to use a
> work-queue for this. I concluded that it wasn't a good idea.
> If a server was down, the manager cold block indefinitely.
> If memory was tight and only one workqueue thread was active,
> this would block other NFS mounts.
So allocate one workqueue per mount?
next prev parent reply other threads:[~2014-07-15 7:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-15 6:39 [PATCH/RFC] NFS: state manager thread must start running NeilBrown
2014-07-15 7:49 ` Christoph Hellwig [this message]
2014-07-15 8:13 ` NeilBrown
2014-07-15 14:51 ` Tejun Heo
2014-07-21 3:35 ` NeilBrown
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=20140715074942.GA6166@infradead.org \
--to=hch@infradead.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tj@kernel.org \
--cc=trond.myklebust@primarydata.com \
/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