From: Ben Hutchings <bhutchings@solarflare.com>
To: Ivan Novick <novickivan@gmail.com>
Cc: netdev@vger.kernel.org, jmatthews@greenplum.com,
Tim Heath <theath@greenplum.com>,
Herbert Xu <herbert@gondor.apana.org.au>
Subject: Re: TCP not triggering a fast retransmit?
Date: Wed, 30 Jun 2010 22:03:49 +0100 [thread overview]
Message-ID: <1277931829.4878.9.camel@localhost> (raw)
In-Reply-To: <AANLkTinJC6uS1GTbKJWL9AlEs2e5GleQvJbTUZrsQHaE@mail.gmail.com>
On Wed, 2010-06-30 at 11:04 -0700, Ivan Novick wrote:
> Hello all,
>
> Attached is a packet capture from my application that is running on
> RedHat Enterprise Linux 5.4
>
> I am seeing a Retransmission timeout but I was hoping this case would
> go into fast retransmit and not RTO.
>
> I am wondering why did the sender not send more data? If the sender
> was to send more data and extend the window then it would seem the
> duplicate acks or SACKS should trigger fast retransmit.
[...]
In that packet capture I see TCP payload lengths which are 2, 3 and 4
times the usual MSS of 1448 bytes, which implies that GRO or LRO is in
use. In RHEL 5.4 the TCP stack does not ACK often enough in this case
because it is missing this change:
commit ff9b5e0f08cb650d113eef0c654f931c0a7ae730
Author: Herbert Xu <herbert@gondor.apana.org.au>
Date: Thu Aug 31 15:11:02 2006 -0700
[TCP]: Fix rcv mss estimate for LRO
Ben.
--
Ben Hutchings, Senior Software Engineer, Solarflare Communications
Not speaking for my employer; that's the marketing department's job.
They asked us to note that Solarflare product names are trademarked.
next prev parent reply other threads:[~2010-06-30 21:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 18:04 TCP not triggering a fast retransmit? Ivan Novick
2010-06-30 19:26 ` Brian Bloniarz
2010-06-30 20:06 ` Mitchell Erblich
2010-06-30 20:14 ` Ivan Novick
2010-06-30 20:43 ` Mitchell Erblich
2010-06-30 21:03 ` Ben Hutchings [this message]
2010-06-30 21:22 ` David Miller
2010-06-30 23:10 ` Mitchell Erblich
2010-07-01 0:27 ` Ivan Novick
2010-07-01 1:23 ` Ben Hutchings
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=1277931829.4878.9.camel@localhost \
--to=bhutchings@solarflare.com \
--cc=herbert@gondor.apana.org.au \
--cc=jmatthews@greenplum.com \
--cc=netdev@vger.kernel.org \
--cc=novickivan@gmail.com \
--cc=theath@greenplum.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).