From: "J. Bruce Fields" <bfields@fieldses.org>
Subject: Re: 2.4 vs 2.6
Date: Tue, 13 Jun 2006 22:15:55 -0400
Message-ID: <20060614021555.GA13425@fieldses.org>
References: <17526.44653.228663.713864@cse.unsw.edu.au>
	<20060526081905.73641.qmail@web51609.mail.yahoo.com>
	<20060526193118.GB17761@fieldses.org>
	<17530.36039.227704.325645@cse.unsw.edu.au>
	<20060529160236.GC6832@fieldses.org>
	<20060530011208.GB12818@sgi.com>
	<20060530015918.GA27940@fieldses.org>
	<17550.12582.742528.454837@cse.unsw.edu.au>
	<20060613204225.GB26315@fieldses.org>
	<1150248571.22282.1450.camel@hole.melbourne.sgi.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: Neil Brown <neilb@suse.de>,
	mehta kiran <kiranmehta1981@yahoo.com>,
	Linux NFS Mailing List <nfs@lists.sourceforge.net>,
	Vijay Chauhan <kernel.vijay@gmail.com>
To: Greg Banks <gnb@melbourne.sgi.com>
In-Reply-To: <1150248571.22282.1450.camel@hole.melbourne.sgi.com>
Sender: nfs-bounces@lists.sourceforge.net
Errors-To: nfs-bounces@lists.sourceforge.net

On Wed, Jun 14, 2006 at 11:29:31AM +1000, Greg Banks wrote:
> There are a couple more considerations.
> 
> First, the list of IP addresses to which a netgroup maps can be
> quite large

Yeah, it's obvious why we need the ip address->netgroup mapping; it's
the netgroup->export options that I was interested in.

> Second, rpc.mountd is single-threaded, and needs to do a blocking
> reverse hostname lookup on every mount and needs to respond to at
> least one upcall shortly afterward.  When you have a thousand
> compute cluster nodes all trying to mount in the same second, this
> gets to be something of a problem.

This should be trivially fixable, shouldn't it?  (Actually, can you run
multiple concurrent mountd's right now?)

--b.


_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs