netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: eric.dumazet@gmail.com
Cc: netdev@vger.kernel.org, soheil@google.com, ncardwell@google.com,
	ycheng@google.com, csg@google.com, vanj@google.com
Subject: Re: [PATCH net-next] tcp: refine tcp_prune_ofo_queue() to not drop all packets
Date: Thu, 18 Aug 2016 23:36:43 -0700 (PDT)	[thread overview]
Message-ID: <20160818.233643.732250691565806768.davem@davemloft.net> (raw)
In-Reply-To: <1471468629.29842.39.camel@edumazet-glaptop3.roam.corp.google.com>

From: Eric Dumazet <eric.dumazet@gmail.com>
Date: Wed, 17 Aug 2016 14:17:09 -0700

> From: Eric Dumazet <edumazet@google.com>
> 
> Over the years, TCP BDP has increased a lot, and is typically
> in the order of ~10 Mbytes with help of clever Congestion Control
> modules.
> 
> In presence of packet losses, TCP stores incoming packets into an out of
> order queue, and number of skbs sitting there waiting for the missing
> packets to be received can match the BDP (~10 Mbytes)
> 
> In some cases, TCP needs to make room for incoming skbs, and current
> strategy can simply remove all skbs in the out of order queue as a last
> resort, incurring a huge penalty, both for receiver and sender.
> 
> Unfortunately these 'last resort events' are quite frequent, forcing
> sender to send all packets again, stalling the flow and wasting a lot of
> resources.
> 
> This patch cleans only a part of the out of order queue in order
> to meet the memory constraints.
> 
> Signed-off-by: Eric Dumazet <edumazet@google.com>

Looks great, applied.

      parent reply	other threads:[~2016-08-19  6:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-17 21:17 [PATCH net-next] tcp: refine tcp_prune_ofo_queue() to not drop all packets Eric Dumazet
2016-08-18  1:10 ` Soheil Hassas Yeganeh
2016-08-18 17:55 ` Yuchung Cheng
2016-08-18 18:05   ` Eric Dumazet
2016-08-18 19:08 ` Neal Cardwell
2016-08-19  6:36 ` David Miller [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=20160818.233643.732250691565806768.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=csg@google.com \
    --cc=eric.dumazet@gmail.com \
    --cc=ncardwell@google.com \
    --cc=netdev@vger.kernel.org \
    --cc=soheil@google.com \
    --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;
as well as URLs for NNTP newsgroup(s).