public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 19:05:03 -0400	[thread overview]
Message-ID: <407F151F.4020703@nortelnetworks.com> (raw)
In-Reply-To: <1082068356.7141.70.camel@lade.trondhjem.org>

Trond Myklebust wrote:
> På to , 15/04/2004 klokka 15:03, skreiv Chris Friesen:
> 
>>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.

> So exactly how would moving that monitoring into the kernel change the
> parameters of the above problem?

I guess I was thinking that if the kernel knew the status of the mounts, 
it could speed things up for userspace apps that don't properly handle 
network filesystems.  Probably not practical though.

We had an interesting time converting some apps that were originally 
using a ramdisk to run with NFS-mounted files.  Since reading from the 
ramdisk never blocked for significant amounts of time, some of the apps 
didn't design for IO delay and behaved poorly the first time we pulled 
the links to the NFS server.

Chris

      reply	other threads:[~2004-04-15 23:05 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
2004-04-15 22:32     ` Trond Myklebust
2004-04-15 23:05       ` Chris Friesen [this message]

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=407F151F.4020703@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox