From: Fan Du <fengyuleidian0615@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Fan Du <fan.du@intel.com>, davem@davemloft.net, netdev@vger.kernel.org
Subject: Re: [PATCH net-next 3/3] ipv4: Create probe timer for tcp PMTU as per RFC4821
Date: Mon, 16 Feb 2015 13:38:43 +0800 [thread overview]
Message-ID: <54E18263.8040002@gmail.com> (raw)
In-Reply-To: <1423830709.4942.17.camel@edumazet-glaptop2.roam.corp.google.com>
于 2015年02月13日 20:31, Eric Dumazet 写道:
> On Fri, 2015-02-13 at 16:16 +0800, Fan Du wrote:
>> >As per RFC4821 7.3. Selecting Probe Size, a probe timer should
>> >be armed once probing has converged. Once this timer expired,
>> >probing again to take advantage of any path PMTU change. The
>> >recommended probing interval is 10 minutes per RFC1981.
>> >
>> >Signed-off-by: Fan Du<fan.du@intel.com>
>> >---
>> > include/net/inet_connection_sock.h | 2 ++
>> > include/net/netns/ipv4.h | 1 +
>> > include/net/tcp.h | 3 +++
>> > net/ipv4/sysctl_net_ipv4.c | 7 +++++++
>> > net/ipv4/tcp.c | 2 ++
>> > net/ipv4/tcp_ipv4.c | 1 +
>> > net/ipv4/tcp_output.c | 23 ++++++++++++++++++++++-
>> > 7 files changed, 38 insertions(+), 1 deletions(-)
>> >
>> >diff --git a/include/net/inet_connection_sock.h b/include/net/inet_connection_sock.h
>> >index 3d0932e..e78e5ab 100644
>> >--- a/include/net/inet_connection_sock.h
>> >+++ b/include/net/inet_connection_sock.h
>> >@@ -126,6 +126,8 @@ struct inet_connection_sock {
>> >
>> > int search_high_sav;
>> > int search_low_sav;
>> >+
>> >+ struct timer_list probe_timer;
>> >
> We certainly wont add yet another timer in tcp socket for such usage.
>
> And a buggy one, since you forgot all the refcounting associated with
> such timers.
oh, embarrassing...
Will place probe timer aside with icsk_delack_timer in struct inet_connection_sock,
and manipulate through sk_reset_timer.
Thanks for the reviewing.
next prev parent reply other threads:[~2015-02-16 5:43 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 [this message]
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=54E18263.8040002@gmail.com \
--to=fengyuleidian0615@gmail.com \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=fan.du@intel.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).