From: Chris Friesen <cfriesen@nortelnetworks.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Fabian Frederick <Fabian.Frederick@skynet.be>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: NFS proc entry
Date: Thu, 15 Apr 2004 18:03:41 -0400 [thread overview]
Message-ID: <407F06BD.3010905@nortelnetworks.com> (raw)
In-Reply-To: <1082065633.7141.52.camel@lade.trondhjem.org>
Trond Myklebust wrote:
> På to , 15/04/2004 klokka 13:25, skreiv Fabian Frederick:
>> Do we have some /proc entry for realtime NFS access point report /
>>client like showmount does with RPC ?
> Exactly what possible justification would there be for putting something
> like that into the kernel?
I agree with you that it's kind of messy to put this in the kernel.
However, with the current setup filesystem monitoring deamons must fork
off a child for each mount, since statfs() can block for many seconds if
the server has gone away.
Chirs
next prev parent reply other threads:[~2004-04-15 22:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-04-15 20:25 NFS proc entry Fabian Frederick
2004-04-15 21:47 ` Trond Myklebust
2004-04-15 22:03 ` Chris Friesen [this message]
2004-04-15 22:32 ` Trond Myklebust
2004-04-15 23:05 ` Chris Friesen
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=407F06BD.3010905@nortelnetworks.com \
--to=cfriesen@nortelnetworks.com \
--cc=Fabian.Frederick@skynet.be \
--cc=linux-kernel@vger.kernel.org \
--cc=trond.myklebust@fys.uio.no \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.