From: "Ogden, Aaron A." <aogden@unocal.com>
To: "Trond Myklebust" <trond.myklebust@fys.uio.no>,
"Lever, Charles" <Charles.Lever@netapp.com>
Cc: <nfs@lists.sourceforge.net>
Subject: RE: ~800 mountpoint limitation
Date: Fri, 17 Oct 2003 12:37:28 -0500 [thread overview]
Message-ID: <6AB920CC10586340BE1674976E0A991D59562D@slexch2.sugarland.unocal.com> (raw)
According to MW and EW (Sun and HP, respectively) this is the way it's
done on Solaris and HPUX so I think it's safe to say it's a proven
concept. You go Trond!! :-D
> I'm not really sure that I buy the argument about the server disks
> getting busy. That will tend to hit you whether or not you are sharing
> RPC slots, since it also ties up server resources.
>=20
> The main point with putting all the transport to a given server on one
> socket is that the UDP/TCP congestion control algorithms can then
> function efficiently. Instead of competing against other packets
> originating from itself, the client only has to deal with competition
> from other clients.
>=20
> Cheers,
> Trond
-------------------------------------------------------
This SF.net email sponsored by: Enterprise Linux Forum Conference & Expo
The Event For Linux Datacenter Solutions & Strategies in The Enterprise
Linux in the Boardroom; in the Front Office; & in the Server Room
http://www.enterpriselinuxforum.com
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2003-10-17 17:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-17 17:37 Ogden, Aaron A. [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-12-15 15:46 ~800 mountpoint limitation 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 16:27 Ogden, Aaron A.
2003-10-14 16:44 ` Trond Myklebust
2003-12-15 13:33 ` Ian Kent
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=6AB920CC10586340BE1674976E0A991D59562D@slexch2.sugarland.unocal.com \
--to=aogden@unocal.com \
--cc=Charles.Lever@netapp.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.