All of lore.kernel.org
 help / color / mirror / Atom feed
From: Olaf Kirch <okir@suse.de>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Ian Kent <raven@themaw.net>, Charles Lever <cel@citi.umich.edu>,
	nfs@lists.sourceforge.net
Subject: Re: [PATCH] Fix xprt_bindresvport range
Date: Thu, 24 Feb 2005 11:14:49 +0100	[thread overview]
Message-ID: <20050224101449.GB11336@suse.de> (raw)
In-Reply-To: <1109218999.11180.49.camel@lade.trondhjem.org>

> Are you referring to the problem of running out of free privileged
> ports?  Sure, but that is not the problem that Olaf's patch attempts to
> address.

Indeed. The patch fixes what I think is a genuine bug (i.e. sunrpc
grabbing ports from the 1-512 range). Of course I added the sysctls to allow
admins a little flexibility in environments where they do run out of
reserved ports, but I'm also aware that this is just a stop-gap measure.

> To address that problem, we certainly also want to add support for
> sharing of sockets to the same server, and there may be further sharing
> schemes that we can implement. For instance, UDP sockets don't have a
> connection protocol, so they can basically talk to anyone.

I think we need to have connection pools to avoid scalability problems.
I was planning to look into this, unless someone else is already working
on it.

> For TCP sockets, we should also consider playing with the TCP_LINGER2
> socket option (to enable us to re-use the port without having to wait
> through a 60 second timeout).

Adding that in mount(8) may help with some usage patterns. In the kernel
I wouldn't expect it to make too much of a difference.

Olaf
-- 
Olaf Kirch   |  --- o --- Nous sommes du soleil we love when we play
okir@suse.de |    / | \   sol.dhoop.naytheet.ah kin.ir.samse.qurax


-------------------------------------------------------
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://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2005-02-24 10:14 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-02-23 16:28 [PATCH] Fix xprt_bindresvport range Olaf Kirch
2005-02-23 16:35 ` Trond Myklebust
2005-02-24  2:59   ` Ian Kent
2005-02-24  4:23     ` Trond Myklebust
2005-02-24 10:14       ` Olaf Kirch [this message]
2005-02-24 18:12         ` Trond Myklebust
2005-02-25  9:28           ` Olaf Kirch
2005-02-25 17:30             ` Trond Myklebust
2005-02-28 11:33               ` Olaf Kirch
2005-02-25  0:54       ` Ian Kent
  -- strict thread matches above, loose matches on Subject: below --
2005-02-23 17:05 Lever, Charles
2005-02-28 16:41 Lever, Charles
2005-02-28 16:57 ` Olaf Kirch

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=20050224101449.GB11336@suse.de \
    --to=okir@suse.de \
    --cc=cel@citi.umich.edu \
    --cc=nfs@lists.sourceforge.net \
    --cc=raven@themaw.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.