All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ogden, Aaron A." <aogden@unocal.com>
To: "Trond Myklebust" <trond.myklebust@fys.uio.no>
Cc: <nfs@lists.sourceforge.net>
Subject: RE: ~800 mountpoint limitation
Date: Tue, 14 Oct 2003 11:27:46 -0500	[thread overview]
Message-ID: <6AB920CC10586340BE1674976E0A991D59560D@slexch2.sugarland.unocal.com> (raw)


Excellent!  I was hoping that you were following the discussion.  It is
something you can fix though?  It seems that RPC may be involved as
well...

Is there any hope of a patch for 2.4.20+ or is this strictly 2.6 code?

-----Original Message-----
From: Trond Myklebust [mailto:trond.myklebust@fys.uio.no]=20
Sent: Tuesday, October 14, 2003 11:06 AM
To: Ogden, Aaron A.
Cc: nfs@lists.sourceforge.net
Subject: Re: [NFS] ~800 mountpoint limitation


>>>>> " " =3D=3D Aaron A Ogden <Ogden> writes:

     > Hello all, This limitation has been confirmed to my
     > satisfaction, I just had a test machine crack at 799
     > mountpoints, so it seems that Chuck's RPC theory may be
     > correct.  Mike Waychison and Eric Werme mentioned that Solaris
     > and HPUX use a multiplexed scheme to reduce the number of ports
     > required for NFS clients, perhaps that is the direction linux
     > NFS/RPC should be heading.

Yes, I already started work on that. In fact a patch already exists on

  http://www.fys.uio.no/~trondmy/src/2.5.73/linux-2.5.73-09-xprt.dif

to multiplex all RPC traffic to a given server/port combination
through a single socket.

It's been put on hold though due to a combination of higher priority
interrupts, and now the 2.6.0 code-freeze...

Cheers,
  Trond


-------------------------------------------------------
This SF.net email is sponsored by: SF.net Giveback Program.
SourceForge.net hosts over 70,000 Open Source Projects.
See the people who have HELPED US provide better services:
Click here: http://sourceforge.net/supporters.php
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

             reply	other threads:[~2003-10-14 16:28 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-14 16:27 Ogden, Aaron A. [this message]
2003-10-14 16:44 ` ~800 mountpoint limitation Trond Myklebust
2003-12-15 13:33   ` Ian Kent
  -- strict thread matches above, loose matches on Subject: below --
2003-12-15 15:46 Ogden, Aaron A.
2003-10-17 17:37 Ogden, Aaron A.
2003-10-17 15:09 Lever, Charles
2003-10-17 16:41 ` Trond Myklebust
2003-10-14 17:03 Ogden, Aaron A.
2003-10-15 13:01 ` Ian Kent
2003-10-14 16:45 Lever, Charles
2003-10-17 14:55 ` Trond Myklebust
2003-10-14 15:51 Ogden, Aaron A.
2003-10-14 16:06 ` Trond Myklebust

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=6AB920CC10586340BE1674976E0A991D59560D@slexch2.sugarland.unocal.com \
    --to=aogden@unocal.com \
    --cc=nfs@lists.sourceforge.net \
    --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.