netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: yzhu1 <Yanjun.Zhu@windriver.com>
To: Fan Du <fan.du@intel.com>, <davem@davemloft.net>
Cc: <netdev@vger.kernel.org>, <fengyuleidian0615@gmail.com>
Subject: Re: [PATCH net-next 1/3] ipv4: Raise tcp PMTU probe mss base size
Date: Fri, 13 Feb 2015 17:49:37 +0800	[thread overview]
Message-ID: <54DDC8B1.1050307@windriver.com> (raw)
In-Reply-To: <1423815405-32644-2-git-send-email-fan.du@intel.com>

backward compatible? :-D

Zhu Yanjun
On 02/13/2015 04:16 PM, Fan Du wrote:
> 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>
> ---
>   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

  reply	other threads:[~2015-02-13  9:49 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-13  8:16 [PATCH net-next 0/3] Small fix for TCP PMTU Fan Du
2015-02-13  8:16 ` [PATCH net-next 1/3] ipv4: Raise tcp PMTU probe mss base size Fan Du
2015-02-13  9:49   ` yzhu1 [this message]
2015-02-16  5:15     ` Fan Du
2015-02-13  8:16 ` [PATCH net-next 2/3] ipv4: Use binary search to choose tcp PMTU probe_size Fan Du
2015-02-13 17:52   ` John Heffner
2015-02-16  5:27     ` Fan Du
2015-02-16 23:59       ` John Heffner
2015-02-13  8:16 ` [PATCH net-next 3/3] ipv4: Create probe timer for tcp PMTU as per RFC4821 Fan Du
2015-02-13  9:59   ` Ying Xue
2015-02-16  5:28     ` Fan Du
2015-02-13 12:31   ` Eric Dumazet
2015-02-16  5:38     ` Fan Du
2015-02-16 12:19       ` Eric Dumazet
2015-02-26  3:49 ` [PATCHv2 net-next 0/4] Small fix for TCP PMTU Fan Du
2015-02-26  3:49   ` [PATCHv2 net-next 1/4] ipv4: Raise tcp PMTU probe mss base size Fan Du
2015-02-26  3:49   ` [PATCHv2 net-next 2/4] ipv4: Use binary search to choose tcp PMTU probe_size Fan Du
2015-02-27 22:17     ` David Miller
2015-02-26  3:49   ` [PATCHv2 net-next 3/4] ipv4: shrink current mss for tcp PMTU blackhole detection Fan Du
2015-02-26  3:49   ` [PATCHv2 net-next 4/4] ipv4: Create probe timer for tcp PMTU as per RFC4821 Fan Du
2015-02-26  4:19     ` Eric Dumazet
2015-02-26  6:24       ` Fan Du
2015-02-26 13:40   ` [PATCHv2 net-next 0/4] Small fix for TCP PMTU David Laight
2015-02-27  5:37     ` Fan Du

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=54DDC8B1.1050307@windriver.com \
    --to=yanjun.zhu@windriver.com \
    --cc=davem@davemloft.net \
    --cc=fan.du@intel.com \
    --cc=fengyuleidian0615@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).