Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: George Amanakis <g_amanakis@yahoo.com>
To: David Lang <david@lang.hm>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] total download rate with many flows
Date: Mon, 13 Nov 2017 21:49:53 -0500	[thread overview]
Message-ID: <daad0484-2c81-a2df-d98e-b3ab8ee8027a@yahoo.com> (raw)
In-Reply-To: <alpine.DEB.2.02.1711131804040.10890@nftneq.ynat.uz>

Dear David,

I agree. My point is that currently ingress mode seems to be dropping 
more packets than necessary to keep senders from bottlenecking the 
connection (when there is a large number of concurrent flows, >8). And 
right now, ingress mode is the only mode that achieves this in 
situations such as Windows updates.

George


On 11/13/2017 9:08 PM, David Lang wrote:
> Ingres and Egress are fundamentally different due to the fact that in 
> ingress mode you are having to throw away data that has successfully 
> traversed the bottleneck (deliberatly wasting your limited resource 
> now to avoid having senders bottleneck the queue on the far side of 
> the link)
>
> in Egress mode, you aren't doing that, and so you can get much closer 
> to the actual bandwidth.
>
> In addition, in Ingress mode, you are always working via second-order 
> effects, you can't slow a transmission directly like you can in egress 
> mode, all you can do is drop packets and wait until the sender 
> notices, retransmits and slows down. Egress has full control of the 
> queues and can send things in any order, and may be able to 
> continually fill the pipe and avoid any timeouts and retransmissions 
> (if the flow is short enough)
>
> David Lang
>


  reply	other threads:[~2017-11-14  2:50 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.905.1509489461.3609.cake@lists.bufferbloat.net>
2017-11-01  0:44 ` Dave Taht
2017-11-01  1:06   ` Antoine Deschênes
2017-11-01  1:41     ` George Amanakis
2017-11-01  3:37     ` George Amanakis
     [not found]     ` <mailman.907.1509507446.3609.cake@lists.bufferbloat.net>
2017-11-01 22:01       ` Dave Taht
2017-11-10 16:32         ` George Amanakis
     [not found]         ` <mailman.964.1510331572.3609.cake@lists.bufferbloat.net>
2017-11-10 20:42           ` Dave Taht
2017-11-10 20:54             ` George Amanakis
     [not found]             ` <mailman.968.1510347301.3609.cake@lists.bufferbloat.net>
     [not found]               ` <CAJq5cE0fsOUZid7peQQYE5qwqBr9GNCx_hYE7dWs4F4UTS=RTA@mail.gmail.com>
2017-11-10 21:50                 ` Jonathan Morton
2017-11-12  3:48                   ` George Amanakis
2017-11-14  1:51                     ` George Amanakis
2017-11-14  1:53                       ` George Amanakis
     [not found]                   ` <mailman.969.1510458543.3609.cake@lists.bufferbloat.net>
2017-11-14  2:08                     ` David Lang
2017-11-14  2:49                       ` George Amanakis [this message]
     [not found]                       ` <mailman.986.1510627800.3609.cake@lists.bufferbloat.net>
2017-11-14 20:11                         ` Dave Taht
2017-11-14 22:13                           ` G. Amanakis
     [not found]                           ` <mailman.987.1510697602.3609.cake@lists.bufferbloat.net>
2017-11-14 22:23                             ` Dave Taht
2017-11-15  4:04                               ` George Amanakis
2017-11-16  4:49                                 ` Dave Taht
2017-11-16  6:52                                   ` Jonathan Morton
     [not found]                                     ` <CACvFP_jGkByNCk=-n4NOxptw59nb8Bsup4Ymd+LbGi6O_WJr5Q@mail.gmail.com>
2017-11-16 17:08                                       ` [Cake] Fwd: " Georgios Amanakis
2017-11-16 23:12                                       ` [Cake] " Jonathan Morton
     [not found] <mailman.1036.1510936271.3609.cake@lists.bufferbloat.net>
2017-11-17 20:05 ` Pete Heist
2017-11-20  8:06   ` Jonathan Morton
2017-11-20  9:07     ` Pete Heist

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

  List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=daad0484-2c81-a2df-d98e-b3ab8ee8027a@yahoo.com \
    --to=g_amanakis@yahoo.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=david@lang.hm \
    /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