From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org
Subject: Re: [PATCH net-next] tcp/dccp: warn user for preferred ip_local_port_range
Date: Wed, 27 May 2015 14:37:22 -0400 (EDT) [thread overview]
Message-ID: <20150527.143722.1854988910324788026.davem@davemloft.net> (raw)
In-Reply-To: <1432751677.4060.423.camel@edumazet-glaptop2.roam.corp.google.com>
From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Wed, 27 May 2015 11:34:37 -0700
> From: Eric Dumazet <edumazet@google.com>
>
> After commit 07f4c90062f8f ("tcp/dccp: try to not exhaust
> ip_local_port_range in connect()") it is advised to have an even number
> of ports described in /proc/sys/net/ipv4/ip_local_port_range
>
> This means start/end values should have a different parity.
>
> Let's warn sysadmins of this, so that they can update their settings
> if they want to.
>
> Suggested-by: David S. Miller <davem@davemloft.net>
> Signed-off-by: Eric Dumazet <edumazet@google.com>
Looks good, applied, thanks Eric.
prev parent reply other threads:[~2015-05-27 18:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 18:34 [PATCH net-next] tcp/dccp: warn user for preferred ip_local_port_range Eric Dumazet
2015-05-27 18:37 ` David 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=20150527.143722.1854988910324788026.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.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).