All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Waychison <Michael.Waychison@Sun.COM>
To: "Ogden, Aaron A." <aogden@unocal.com>
Cc: autofs@linux.kernel.org, Ian Kent <raven@themaw.net>
Subject: Re: RE: autofs scalability
Date: Wed, 03 Dec 2003 15:01:39 -0500	[thread overview]
Message-ID: <3FCE4123.8050301@sun.com> (raw)
In-Reply-To: <6AB920CC10586340BE1674976E0A991DE22E18@slexch2.sugarland.unocal.com>


[-- Attachment #1.1: Type: text/plain, Size: 1403 bytes --]

Ogden, Aaron A. wrote:

>Hello all,
>I was reading through Joe Pranevich's "Wonderful World of Linux 2.6" and
>I came across this, I thought you might find it interesting. (source:
>http://kniggit.net/wwol26.html)  The "Network Filesystems" section makes
>for interesting reading as well.  If I am reading this correctly, the
>'unnamed device' limit has been raised from 256 to 4096 in kernel 2.6,
>can anyone confirm this?  
>

No.  The major count went from 256 -> 4096.  The minor count went from 
256 to 1048576.  The maximum pseudo-block-device limit is still 256 
currently.

>If this is the case the only barrier left to
>remove is the RPC port limitation of ~800 open ports.  If the
>connections were multiplexed such that all connections to a given server
>used the same port then 800 ports would stretch a lot farther than they
>do now...
>
>  
>
Yes.  This has been identified as an upper limit.  :(

But you're right, these two limits are blocking being able to mount 
large numbers of NFS mounts.


-- 
Mike Waychison
Sun Microsystems, Inc.
1 (650) 352-5299 voice
1 (416) 202-8336 voice
mailto: Michael.Waychison@Sun.COM
http://www.sun.com

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE:  The opinions expressed in this email are held by me, 
and may not represent the views of Sun Microsystems, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ 


[-- Attachment #1.2: Type: application/pgp-signature, Size: 251 bytes --]

[-- Attachment #2: Type: text/plain, Size: 140 bytes --]

_______________________________________________
autofs mailing list
autofs@linux.kernel.org
http://linux.kernel.org/mailman/listinfo/autofs

  parent reply	other threads:[~2003-12-03 20:01 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-03 19:19 autofs scalability Ogden, Aaron A.
2003-12-03 19:43 ` Tim Hockin
2003-12-04  1:37   ` Ian Kent
2003-12-04 19:12     ` Tim Hockin
2003-12-04 20:04       ` H. Peter Anvin
2003-12-04 22:37         ` Tim Hockin
2003-12-04 23:09           ` H. Peter Anvin
2003-12-04 23:12             ` Tim Hockin
2003-12-03 20:01 ` Mike Waychison [this message]
2003-12-04  1:35 ` Ian Kent

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=3FCE4123.8050301@sun.com \
    --to=michael.waychison@sun.com \
    --cc=aogden@unocal.com \
    --cc=autofs@linux.kernel.org \
    --cc=raven@themaw.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 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.