Subject: Re: NFS proc entry
From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Chris Friesen <cfriesen@nortelnetworks.com>
Cc: Fabian Frederick <Fabian.Frederick@skynet.be>,
       lkml <linux-kernel@vger.kernel.org>
In-Reply-To: <407F06BD.3010905@nortelnetworks.com>
References: <1082060754.9112.2.camel@bluerhyme.real3>
	 <1082065633.7141.52.camel@lade.trondhjem.org>
	 <407F06BD.3010905@nortelnetworks.com>
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8BIT
Message-Id: <1082068356.7141.70.camel@lade.trondhjem.org>
Mime-Version: 1.0
Date: Thu, 15 Apr 2004 15:32:36 -0700
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 820
Lines: 18

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? The kernel has exactly the same issues:
The only way it can tell if the server is down is by probing the
connection and timing out. That's the reason why those userland child
processes end up hanging in the first place.

Cheers,
  Trond
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/