netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: edumazet@google.com
Cc: netdev@vger.kernel.org, ncardwell@google.com, ycheng@google.com,
	eric.dumazet@gmail.com
Subject: Re: [PATCH v2 net-next] tcp-tso: do not split TSO packets at retransmit time
Date: Sun, 24 Apr 2016 14:44:20 -0400 (EDT)	[thread overview]
Message-ID: <20160424.144420.594314082130628842.davem@davemloft.net> (raw)
In-Reply-To: <1461261323-14355-1-git-send-email-edumazet@google.com>

From: Eric Dumazet <edumazet@google.com>
Date: Thu, 21 Apr 2016 10:55:23 -0700

> Linux TCP stack painfully segments all TSO/GSO packets before retransmits.
> 
> This was fine back in the days when TSO/GSO were emerging, with their
> bugs, but we believe the dark age is over.
> 
> Keeping big packets in write queues, but also in stack traversal
> has a lot of benefits.
>  - Less memory overhead, because write queues have less skbs
>  - Less cpu overhead at ACK processing.
>  - Better SACK processing, as lot of studies mentioned how
>    awful linux was at this ;)
>  - Less cpu overhead to send the rtx packets
>    (IP stack traversal, netfilter traversal, drivers...)
>  - Better latencies in presence of losses.
>  - Smaller spikes in fq like packet schedulers, as retransmits
>    are not constrained by TCP Small Queues.
> 
> 1 % packet losses are common today, and at 100Gbit speeds, this
> translates to ~80,000 losses per second.
> Losses are often correlated, and we see many retransmit events
> leading to 1-MSS train of packets, at the time hosts are already
> under stress.
> 
> Signed-off-by: Eric Dumazet <edumazet@google.com>
> Acked-by: Yuchung Cheng <ycheng@google.com>

Applied, thanks Eric.

  reply	other threads:[~2016-04-24 18:44 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-04-21 17:55 [PATCH v2 net-next] tcp-tso: do not split TSO packets at retransmit time Eric Dumazet
2016-04-24 18:44 ` David Miller [this message]
  -- strict thread matches above, loose matches on Subject: below --
2016-04-25 17:39 [PATCH net-next 0/2] net: avoid some atomic ops when FASYNC is not used Eric Dumazet
2016-04-25 17:39 ` [PATCH v2 net-next] tcp-tso: do not split TSO packets at retransmit time Eric Dumazet
2016-04-25 17:43   ` 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=20160424.144420.594314082130628842.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --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;
as well as URLs for NNTP newsgroup(s).