From: David Miller <davem@davemloft.net>
To: yanhaishuang@cmss.chinamobile.com
Cc: kuznet@ms2.inr.ac.ru, edumazet@google.com, weiwan@google.com,
lucab@debian.org, netdev@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v5 4/4] ipv4: Namespaceify tcp_fastopen_blackhole_timeout knob
Date: Thu, 28 Sep 2017 10:48:01 -0700 (PDT) [thread overview]
Message-ID: <20170928.104801.364432233895912663.davem@davemloft.net> (raw)
In-Reply-To: <1506483343-11544-4-git-send-email-yanhaishuang@cmss.chinamobile.com>
From: Haishuang Yan <yanhaishuang@cmss.chinamobile.com>
Date: Wed, 27 Sep 2017 11:35:43 +0800
> Different namespace application might require different time period in
> second to disable Fastopen on active TCP sockets.
>
> Tested:
> Simulate following similar situation that the server's data gets dropped
> after 3WHS.
> C ---- syn-data ---> S
> C <--- syn/ack ----- S
> C ---- ack --------> S
> S (accept & write)
> C? X <- data ------ S
> [retry and timeout]
>
> And then print netstat of TCPFastOpenBlackhole, the counter increased as
> expected when the firewall blackhole issue is detected and active TFO is
> disabled.
> # cat /proc/net/netstat | awk '{print $91}'
> TCPFastOpenBlackhole
> 1
>
> Signed-off-by: Haishuang Yan <yanhaishuang@cmss.chinamobile.com>
Applied.
next prev parent reply other threads:[~2017-09-28 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-27 3:35 [PATCH v5 1/4] ipv4: Namespaceify tcp_fastopen knob Haishuang Yan
2017-09-27 3:35 ` [PATCH v5 2/4] ipv4: Remove the 'publish' logic in tcp_fastopen_init_key_once Haishuang Yan
2017-09-28 17:47 ` David Miller
2017-09-27 3:35 ` [PATCH v5 3/4] ipv4: Namespaceify tcp_fastopen_key knob Haishuang Yan
2017-09-28 17:47 ` David Miller
2017-09-27 3:35 ` [PATCH v5 4/4] ipv4: Namespaceify tcp_fastopen_blackhole_timeout knob Haishuang Yan
2017-09-28 17:48 ` David Miller [this message]
2017-09-28 17:47 ` [PATCH v5 1/4] ipv4: Namespaceify tcp_fastopen knob 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=20170928.104801.364432233895912663.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuznet@ms2.inr.ac.ru \
--cc=linux-kernel@vger.kernel.org \
--cc=lucab@debian.org \
--cc=netdev@vger.kernel.org \
--cc=weiwan@google.com \
--cc=yanhaishuang@cmss.chinamobile.com \
/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).