From: Bernd Petrovitsch <bernd@firmix.at>
To: Daniel Phillips <phillips@phunq.net>
Cc: "J. Bruce Fields" <bfields@fieldses.org>, linux-kernel@vger.kernel.org
Subject: Re: A peek at the future of storage
Date: Wed, 12 Dec 2007 19:39:25 +0100 [thread overview]
Message-ID: <1197484765.32283.106.camel@tara.firmix.at> (raw)
In-Reply-To: <200712121002.44643.phillips@phunq.net>
On Mit, 2007-12-12 at 10:02 -0800, Daniel Phillips wrote:
> On Wednesday 12 December 2007 09:46, J. Bruce Fields wrote:
[...]
> > People have proposed writing a daemon that just reads
> > /proc/net/rpc/nfsd periodically and uses that to adjust the number of
> > threads from userspace, probably subject to some limits in a config
> > file someplace. (Think that could do the job, or is there some reason
[...]
> So how would a userspace daemon know that kernel is blocking and new
> threads are needed? In kernel this is pretty easy: when a new request
> arrives, look on the thread list and if none are available, generate a
> new one. Something special needs to be done to handle the case where
> there are no threads available because they are all piled up on a
> semaphore due to, for example, somebody unplugging the network cable
> for a remote disk. We have to avoid generating infinite threads in
> that case. Ideas?
Add a sysctl configurable maximum number of NFS threads and default it
to 8 (or whatever now the default value is).
And one wants probably some logic to kill them again if they are not
used long enough. And then you need/want another variable for the
minimum number of NFS threads around.
Bernd
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services
next prev parent reply other threads:[~2007-12-12 18:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-12 16:46 Daniel Phillips
2007-12-12 17:46 ` J. Bruce Fields
2007-12-12 18:02 ` Daniel Phillips
2007-12-12 18:39 ` Bernd Petrovitsch [this message]
2007-12-12 19:57 ` J. Bruce Fields
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=1197484765.32283.106.camel@tara.firmix.at \
--to=bernd@firmix.at \
--cc=bfields@fieldses.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@phunq.net \
/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®