From: "David S. Miller" <davem@redhat.com>
To: Stephen Hemminger <shemminger@osdl.org>
Cc: netdev@oss.sgi.com
Subject: Re: [RFC] tcp ephemeral port selection
Date: Mon, 25 Oct 2004 16:34:18 -0700 [thread overview]
Message-ID: <20041025163418.30c703e2.davem@redhat.com> (raw)
In-Reply-To: <20041011171422.65f88472@zqx3.pdx.osdl.net>
On Mon, 11 Oct 2004 17:14:22 -0700
Stephen Hemminger <shemminger@osdl.org> wrote:
> Here is a test patch which changes how TCP ephemeral ports are
> selected from a simple roving pointer to:
> * net_random() as starting point when doing pure local
> searchs.
> * use md hash (like isn) when doing connection based
> assignments with a rover
>
> This is *not* for 2.6.9 but wanted to get it out for comment for
> future versions.
I'm not totally against this kind of idea at all.
I hope we don't run into situations with the new
code where we don't actually check the whole port
range due to some logic error or similar.
Another thing we need to eventually do is allow
allocation into the local port space more completely.
Even if every local port has one user, we could still
allocate some ports if the daddr/dport is known and
is different from the existing user.
prev parent reply other threads:[~2004-10-25 23:34 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-12 0:14 [RFC] tcp ephemeral port selection Stephen Hemminger
2004-10-25 23:34 ` David S. Miller [this message]
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=20041025163418.30c703e2.davem@redhat.com \
--to=davem@redhat.com \
--cc=netdev@oss.sgi.com \
--cc=shemminger@osdl.org \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).