Netdev List
 help / color / mirror / Atom feed
From: Eric Dumazet <eric.dumazet@gmail.com>
To: David Miller <davem@davemloft.net>
Cc: netdev@vger.kernel.org, ycheng@google.com, ncardwell@google.com,
	nanditad@google.com, vanj@google.com
Subject: Re: [PATCH] tcp: preserve ACK clocking in TSO
Date: Fri, 22 Mar 2013 07:52:30 -0700	[thread overview]
Message-ID: <1363963950.4431.65.camel@edumazet-glaptop> (raw)
In-Reply-To: <20130322.103435.879689479406836333.davem@davemloft.net>

On Fri, 2013-03-22 at 10:34 -0400, David Miller wrote:

> I always wondered about this, good catch.
> 
> Applied and queued up for -stable, thanks!

It took me a while to see the light.

I was trying to reduce the time limit (2 ticks -> 1 tick), or remove
tso_deferred field to use lsndtime instead.

Then, before cooking the patch for net-next, I finally understood the
problem.

Thanks

      reply	other threads:[~2013-03-22 14:52 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-22  3:36 [PATCH] tcp: preserve ACK clocking in TSO Eric Dumazet
2013-03-22 14:34 ` David Miller
2013-03-22 14:52   ` Eric Dumazet [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=1363963950.4431.65.camel@edumazet-glaptop \
    --to=eric.dumazet@gmail.com \
    --cc=davem@davemloft.net \
    --cc=nanditad@google.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=vanj@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox