From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: <cake@lists.bufferbloat.net>
Subject: [Cake] cake review comments cake_drop
Date: Sat, 3 Oct 2015 20:42:00 +0100 [thread overview]
Message-ID: <56102F88.8070201@darbyshire-bryant.me.uk> (raw)
[-- Attachment #1: Type: text/plain, Size: 1089 bytes --]
Hello All,
On 18th Aug (before I'd subscribed to the list), Dave posted a message
about reviewing cake
https://lists.bufferbloat.net/pipermail/cake/2015-August/000364.html
In it he mentioned a change to cake_drop:
"
I would like cake_drop to be evaluated with some less exaustive
search. It also looks wrong
for(j=0; j < CAKE_MAX_CLASSES; j++) {
fqcd = &q->classes[j];
CAKE_MAX_CLASSES should actually be q->class_cnt here; I think. I am
unsure if other references to it are correct in face of changes, on
cleanup"
After making the change and nearly submitting a pull request I've
thought about this some more and to be blunt it makes me nervous. My
concern is what happens if cake is changed from say a diffserv8 config
to a single class(bin) config and for whatever reason 'cake_drop' is
called. with diffserv8 the fat flow is likely to be in a class(bin)
higher than the first....cake_drop would now only check the first class
for the fat flow and possibly not find anything to drop.... I fear what
happens next!
Kevin
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4816 bytes --]
next reply other threads:[~2015-10-03 19:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-03 19:42 Kevin Darbyshire-Bryant [this message]
2015-10-04 9:03 ` Jonathan Morton
2015-10-04 10:56 ` Sebastian Moeller
2015-10-04 17:46 ` Kevin Darbyshire-Bryant
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=56102F88.8070201@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=cake@lists.bufferbloat.net \
/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