From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] cake review comments cake_drop
Date: Sun, 4 Oct 2015 18:46:57 +0100 [thread overview]
Message-ID: <56116611.8050907@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <94F988FA-894E-4F04-B5BC-4BF6539D0730@gmx.de>
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
On 04/10/15 11:56, Sebastian Moeller wrote:
> Hi Jonathan, hi Kevin,
>
>
> On Oct 4, 2015, at 11:03 , Jonathan Morton <chromatix99@gmail.com> wrote:
>
>> I remember changing cake_drop so that it iterated over the list of active flows rather than the whole potential array. Hence an inactive class, which has no active queues, costs nothing to iterate over. Usually the total number of active queues is tolerably small.
> Ah, so there is the answer to my question ;) Jonathan, which of the public repositories is the closest to your internal version, so which is the semi-official one?
It is exists in Dave's repo. It iterates over the 'old_flows' and
'new_flows' lists for each class looking for the one in most 'distress',
inherently if there's active data to be found it should be on one of
those lists.
In cpu cycle pedant mode, checking for a null list on a set of classes
we know are going to be empty is unnecessary, in a single class config
that's 7 (actually 14) null list searches we don't have to do. I'm sure
it's not much of a saving but every cycle helps.
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4816 bytes --]
next prev parent reply other threads:[~2015-10-04 17:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-03 19:42 Kevin Darbyshire-Bryant
2015-10-04 9:03 ` Jonathan Morton
2015-10-04 10:56 ` Sebastian Moeller
2015-10-04 17:46 ` Kevin Darbyshire-Bryant [this message]
2015-10-05 7:27 ` Sebastian Moeller
2015-10-04 10:50 ` Sebastian Moeller
2015-10-04 17:23 ` Kevin Darbyshire-Bryant
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=56116611.8050907@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=cake@lists.bufferbloat.net \
--cc=moeller0@gmx.de \
/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