From: Rick Jones <rick.jones2@hp.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: "David Miller" <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
"Perry Lorier" <perryl@google.com>,
"Matt Mathis" <mattmathis@google.com>,
"Yuchung Cheng" <ycheng@google.com>,
"Neal Cardwell" <ncardwell@google.com>,
"Tom Herbert" <therbert@google.com>,
"Wilmer van der Gaast" <wilmer@google.com>,
"Dave Täht" <dave.taht@bufferbloat.net>,
"Ankur Jain" <jankur@google.com>
Subject: Re: [PATCH net-next] tcp: be more strict before accepting ECN negociation
Date: Fri, 04 May 2012 11:48:49 -0700 [thread overview]
Message-ID: <4FA42491.2020104@hp.com> (raw)
In-Reply-To: <1336155815.3752.365.camel@edumazet-glaptop>
On 05/04/2012 11:23 AM, Eric Dumazet wrote:
> On Fri, 2012-05-04 at 11:09 -0700, Rick Jones wrote:
>> What sort of networks were these? Any chance it was some sort of
>> attempt to add ECN to FastOpen?
>
> Nothing to do with fastopen.
>
> Just take a look at a random http server and sample all SYN packets it
> receives.
>
> Some of them have TOS bits 0 or 1 set, or even both bits set.
I'll fire-up tcpdump on netperf.org:
tcpdump -i eth0 -vvv '(tcp[tcpflags] & tcp-syn != 0) && (ip[1] != 0x0)'
and see what appears.
rick
next prev parent reply other threads:[~2012-05-04 18:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 15:14 [PATCH net-next] tcp: be more strict before accepting ECN negociation Eric Dumazet
2012-05-04 15:54 ` Neal Cardwell
2012-05-04 16:06 ` David Miller
2012-05-04 18:09 ` Rick Jones
2012-05-04 18:23 ` Eric Dumazet
2012-05-04 18:48 ` Rick Jones [this message]
2012-05-04 19:05 ` Eric Dumazet
2012-05-04 20:20 ` Rick Jones
2012-05-04 20:36 ` Rick Jones
2012-05-04 20:49 ` Eric Dumazet
2012-05-04 21:01 ` Rick Jones
2012-05-04 21:14 ` Eric Dumazet
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=4FA42491.2020104@hp.com \
--to=rick.jones2@hp.com \
--cc=dave.taht@bufferbloat.net \
--cc=davem@davemloft.net \
--cc=eric.dumazet@gmail.com \
--cc=jankur@google.com \
--cc=mattmathis@google.com \
--cc=ncardwell@google.com \
--cc=netdev@vger.kernel.org \
--cc=perryl@google.com \
--cc=therbert@google.com \
--cc=wilmer@google.com \
--cc=ycheng@google.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 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.