From: Mike Waychison <Michael.Waychison@Sun.COM>
To: "Lever, Charles" <Charles.Lever@netapp.com>
Cc: Olaf Kirch <okir@suse.de>, nfs@lists.sourceforge.net
Subject: Re: [PATCH] xprt sharing (was Re: xprt_bindresvport)
Date: Wed, 08 Dec 2004 16:58:00 -0500 [thread overview]
Message-ID: <41B778E8.7000602@sun.com> (raw)
In-Reply-To: <482A3FA0050D21419C269D13989C61130435EC70@lavender-fe.eng.netapp.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Lever, Charles wrote:
>>>but also notice this cuts the usable port range in half
>>
>>(from ~800 to
>>
>>>~420). we need some form of mitigation to ensure we aren't
>>
>>limiting the
>>
>>>number of NFS mounts a client can have.
>>
>>This has been bugging me for a while. The fact that we are limitting
>>ourselves to a single nfs mount per port. From what I can
>>tell, Solaris
>>shares the transports between nfs mounts from the same server
>>and saves
>>themselves a lot of trouble with running out of port numbers
>>in doing so.
>>
>>The attached patch does the same for Linux against 2.6.9. We share
>>xprts from existing connections, effectively removing any limit on the
>>number of nfs mounts we have in the system.
>>
>>The only thing to worry about now is any talking to the portmapper or
>>mountd from userspace using tcp, which will put the reserved ports in
>>TIME_WAIT state. This can limit the 'speed' at which we
>>mount many mounts.
>
>
> we're looking at a similar solution. we want to make sure we don't
> limit the scalability of everyone's mount point by making them all
> funnel through a single slot table.
>
Can you post any work in progress for this? The xprt patch I posted
was written a while ago, and I just realized this afternoon that it
doesn't seem to do the right thing for tcp sockets that are autoclosed.
If you have a similar patch that works, it would save me the trouble ;)
- --
Mike Waychison
Sun Microsystems, Inc.
1 (650) 352-5299 voice
1 (416) 202-8336 voice
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
NOTICE: The opinions expressed in this email are held by me,
and may not represent the views of Sun Microsystems, Inc.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBt3jodQs4kOxk3/MRArXNAKCaahtv7uNfhX2n2yaz/N3D18t0vgCfSOLa
rOARY+qtJrFfWOtb0m18cSk=
=HlXX
-----END PGP SIGNATURE-----
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://productguide.itmanagersjournal.com/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2004-12-08 21:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-08 19:08 [PATCH] xprt sharing (was Re: xprt_bindresvport) Lever, Charles
2004-12-08 21:58 ` Mike Waychison [this message]
2004-12-09 11:22 ` Olaf Kirch
2004-12-09 13:33 ` Trond Myklebust
2004-12-09 13:41 ` Olaf Kirch
-- strict thread matches above, loose matches on Subject: below --
2004-12-09 14:03 Lever, Charles
2004-12-09 8:54 Peter Åstrand
2004-12-09 11:14 ` Olaf Kirch
2004-12-08 22:00 Lever, Charles
2004-12-08 14:33 xprt_bindresvport Lever, Charles
2004-12-08 18:17 ` [PATCH] xprt sharing (was Re: xprt_bindresvport) Mike Waychison
2004-12-09 11:31 ` Olaf Kirch
2004-12-09 13:36 ` Trond Myklebust
2004-12-09 13:44 ` Olaf Kirch
2004-12-09 16:20 ` Trond Myklebust
2004-12-09 19:34 ` Dan Stromberg
2004-12-09 21:33 ` Trond Myklebust
2004-12-09 22:29 ` Dan Stromberg
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=41B778E8.7000602@sun.com \
--to=michael.waychison@sun.com \
--cc=Charles.Lever@netapp.com \
--cc=nfs@lists.sourceforge.net \
--cc=okir@suse.de \
/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.