From: Fan Du <fan.du@intel.com>
To: jheffner@psc.edu
Cc: davem@davemloft.net, edumazet@google.com, netdev@vger.kernel.org,
fengyuleidian0615@gmail.com
Subject: [PATCHv5 net-next 1/4] ipv4: Raise tcp PMTU probe mss base size
Date: Fri, 6 Mar 2015 11:18:22 +0800 [thread overview]
Message-ID: <1425611905-28503-2-git-send-email-fan.du@intel.com> (raw)
In-Reply-To: <1425611905-28503-1-git-send-email-fan.du@intel.com>
Quotes from RFC4821 7.2. Selecting Initial Values
It is RECOMMENDED that search_low be initially set to an MTU size
that is likely to work over a very wide range of environments. Given
today's technologies, a value of 1024 bytes is probably safe enough.
The initial value for search_low SHOULD be configurable.
Moreover, set a small value will introduce extra time for the search
to converge. So set the initial probe base mss size to 1024 Bytes.
Signed-off-by: Fan Du <fan.du@intel.com>
Acked-by: John Heffner <johnwheffner@gmail.com>
---
include/net/tcp.h | 2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/include/net/tcp.h b/include/net/tcp.h
index 8d6b983..7b57e5b 100644
--- a/include/net/tcp.h
+++ b/include/net/tcp.h
@@ -65,7 +65,7 @@ void tcp_time_wait(struct sock *sk, int state, int timeo);
#define TCP_MIN_MSS 88U
/* The least MTU to use for probing */
-#define TCP_BASE_MSS 512
+#define TCP_BASE_MSS 1024
/* After receiving this amount of duplicate ACKs fast retransmit starts. */
#define TCP_FASTRETRANS_THRESH 3
--
1.7.1
next prev parent reply other threads:[~2015-03-06 3:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-06 3:18 [PATCHv5 net-next 0/4] Improvements for TCP PMTU Fan Du
2015-03-06 3:18 ` Fan Du [this message]
2015-03-06 3:18 ` [PATCHv5 net-next 2/4] ipv4: Use binary search to choose tcp PMTU probe_size Fan Du
2015-03-06 3:18 ` [PATCHv5 net-next 3/4] ipv4: Create probe timer for tcp PMTU as per RFC4821 Fan Du
2015-03-07 18:02 ` Ben Hutchings
2015-03-06 3:18 ` [PATCHv5 net-next 4/4] ipv4: Documenting two sysctls for tcp PMTU probe Fan Du
2015-03-06 19:58 ` [PATCHv5 net-next 0/4] Improvements for TCP PMTU David Miller
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=1425611905-28503-2-git-send-email-fan.du@intel.com \
--to=fan.du@intel.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fengyuleidian0615@gmail.com \
--cc=jheffner@psc.edu \
--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).