From: Fan Du <fengyuleidian0615@gmail.com>
To: David Laight <David.Laight@ACULAB.COM>
Cc: 'Fan Du' <fan.du@intel.com>,
"johnwheffner@gmail.com" <johnwheffner@gmail.com>,
"edumazet@google.com" <edumazet@google.com>,
"davem@davemloft.net" <davem@davemloft.net>,
"netdev@vger.kernel.org" <netdev@vger.kernel.org>
Subject: Re: [PATCHv2 net-next 0/4] Small fix for TCP PMTU
Date: Fri, 27 Feb 2015 13:37:44 +0800 [thread overview]
Message-ID: <54F002A8.307@gmail.com> (raw)
In-Reply-To: <063D6719AE5E284EB5DD2968C1650D6D1CAEEABA@AcuExch.aculab.com>
于 2015年02月26日 21:40, David Laight 写道:
> From: Fan Du
>> >This patchset performs some small fix and enhancement
>> >for current TCP PMTU as per RFC4821 with below changes:
>> >
>> >Patch1/4: Set probe mss base to 1024 Bytes per RFC4821
>> >Patch2/4: Do not double probe_size for each probing,
>> > use a simple binary search to gain maximum performance.
>> >Patch3/4: When it comes to blackhole detection, shrink current
>> > mss for next probing.
>> >Patch4/4: Create a probe timer to detect enlarged path MTU.
> Isn't the most likely problem PPPoE blackholes?
No.
It's used to probe a optimal pmtu value for vxlan tunnel when ICMP message
is not available. Refer patch2/4 for test summary.
> Where a reduction of the PMTU from 1500 to (IIRC) 1492 is
> all that is required?
>
> Would seem appropriate to test that value reasonable quickly.
prev parent reply other threads:[~2015-02-27 5:42 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
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 [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=54F002A8.307@gmail.com \
--to=fengyuleidian0615@gmail.com \
--cc=David.Laight@ACULAB.COM \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fan.du@intel.com \
--cc=johnwheffner@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 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.