Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave@taht.net>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] [RFC PATCH 2/3] Add cake related includes and source files
Date: Tue, 21 Nov 2017 10:59:57 -0800	[thread overview]
Message-ID: <873757v4nm.fsf@nemesis.taht.net> (raw)
In-Reply-To: <91830311-fea3-cb03-be2e-b132ae54ad89@gmail.com> (Jonathan Morton's message of "Tue, 21 Nov 2017 00:52:08 +0200")

Jonathan Morton <chromatix99@gmail.com> writes:

> On 17/11/17 21:52, Dave Taht wrote:
>> Actually using **to_free sanely (here, in qdisc_reduce_backlog, etc)
>> would be good. I like very much how fq_codel does bulk dropping now.
>>
>> I think, but am unsure, that the whole heap concept would just "go",
>> in that case.
>
> I don't see how.

My principal point was that the bulk_drop facility now in fq_codel was
very cpu efficient. I'm willing to keep this, but I'd like to see it
benchmarked under the same udp_flood scenarios as what prompted that
change to fq_codel - Say, a 1Gbit flood into a 10 or a 100Mbit shaped
connection.


> The max-heap is not used to keep track of packets to drop, but which queue is
> the longest.  If a single flow goes completely crazy, that allows dropping a lot
> of packets from *that* queue without having to search over the others every
> time.  At the same time, if the queues are more evenly filled, it still allows
> the longest queues to be trimmed without overly penalising whichever queue
> happened to get caught at the wrong moment.
>
> In cases where several packets need to be dropped to maintain the backlog limit,
> those packets already end up on 'to_free' correctly. Isn't that how it's
> supposed to work?

  parent reply	other threads:[~2017-11-21 19:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-17 19:11 [Cake] [RFC PATCH 0/3] Cake patches for net-next Dave Taht
2017-11-17 19:11 ` [Cake] [RFC PATCH 1/3] Add cake to pkt_sched.h Dave Taht
2017-11-17 19:11 ` [Cake] [RFC PATCH 2/3] Add cake related includes and source files Dave Taht
2017-11-17 19:52   ` Dave Taht
     [not found]     ` <91830311-fea3-cb03-be2e-b132ae54ad89@gmail.com>
2017-11-21 18:59       ` Dave Taht [this message]
     [not found]     ` <dbf49d41-27e1-5d4c-ad23-093d3d2d442e@gmail.com>
2017-11-21 19:03       ` Dave Taht
     [not found]     ` <f7a57f62-9b61-5e4f-6734-dc92f2758d2f@gmail.com>
2017-11-21 19:04       ` Dave Taht
     [not found]     ` <fe13b27c-223f-f9d2-b153-44fbe388ff50@gmail.com>
2017-11-21 19:05       ` Dave Taht
     [not found]     ` <5fbd8b62-f557-d9f6-0396-8bd9135b7c74@gmail.com>
2017-11-21 19:07       ` Dave Taht
2017-11-17 19:11 ` [Cake] [RFC PATCH 3/3] Add support for building the new cake qdisc Dave Taht
2017-11-17 19:21   ` Toke Høiland-Jørgensen
2017-11-17 19:55     ` Dave Taht

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=873757v4nm.fsf@nemesis.taht.net \
    --to=dave@taht.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.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