From: "J. Bruce Fields" <bfields@fieldses.org>
To: Neil Brown <neilb@suse.de>
Cc: Tim Gardner <tim.gardner@canonical.com>,
linux-nfs@vger.kernel.org,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Trond.Myklebust@netapp.com
Subject: Re: nfsd deadlock, 2.6.36-rc3
Date: Wed, 1 Sep 2010 17:05:55 -0400 [thread overview]
Message-ID: <20100901210555.GB10507@fieldses.org> (raw)
In-Reply-To: <20100902065551.079e297c@notabene>
On Thu, Sep 02, 2010 at 06:55:51AM +1000, Neil Brown wrote:
> On Wed, 1 Sep 2010 12:54:01 -0400
> "J. Bruce Fields" <bfields@fieldses.org> wrote:
> > For that reason we just don't support loopback mounts--they're OK for
> > light testing, but it would be difficult to make them completely robust
> > under load.
>
> I wonder if we could use 'containers' to partition available memory between
> 'nfsd threads' and 'everything else'?? Probably not worth the effort.
cgroups, I don't know, I guess the essential thing would be to make sure
that nfsd has the resources it needs to make forward progress, however
slowly--even if it means, for example, only enough to keep a single
thread processing requests.
--b.
next prev parent reply other threads:[~2010-09-01 21:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-01 15:39 nfsd deadlock, 2.6.36-rc3 Tim Gardner
2010-09-01 16:54 ` J. Bruce Fields
2010-09-01 20:55 ` Neil Brown
2010-09-01 21:05 ` J. Bruce Fields [this message]
2010-09-01 21:11 ` Tim Gardner
2010-09-01 21:13 ` J. Bruce Fields
2010-09-02 15:13 ` Tim Gardner
2010-09-08 16:52 ` Tim Gardner
2010-09-08 17:50 ` J. Bruce Fields
2010-09-03 19:12 ` Maciej Rutecki
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=20100901210555.GB10507@fieldses.org \
--to=bfields@fieldses.org \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=neilb@suse.de \
--cc=tim.gardner@canonical.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