From: Sebastian Moeller <moeller0@gmx.de>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Stranger target behaviour
Date: Sun, 1 Nov 2015 18:48:29 +0100 [thread overview]
Message-ID: <5E484E77-C716-4703-940B-C3D2F08809B6@gmx.de> (raw)
In-Reply-To: <56364975.1030606@darbyshire-bryant.me.uk>
Hi Kevin,
On Nov 1, 2015, at 18:18 , Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> wrote:
> On 01/11/15 16:05, Sebastian Moeller wrote:
>> Dear friends of cake,
>>
>>> [...]
>> I believe I just fixed this by initializing target in sch_cake to "interval >> 4”, I opted for the calculation instead of the simple number 6250 to sort of document the pattern and tried to put in a comment explaining why this is okay with codel's theory. Please note, I did not really test this, so for all I know it might break spectacularly...
> Looks ok to me, though the optimising compiler likely will turn that
> calculation into a constant 6250 anyway ;-)
And that is fine it really is to document the fact for the source reader and to catch the hypothetical case that the default interval will be increased in the future...
> Only comment would be
> 'watch your line length' - no lines over 78 chars ideally in the
> kernel.
Well, the powers that be need to decide, I believe the comment is helpful enough to having made it, but insignificant enough to not warrant its dedicated line or block of lines. First let’s see whether the comment survives in its verbosity and then care for style. That said, I am happy to keep monitoring this and potentially make the change.
> On that note I've just committed some checkpatch
> style/formatting related changes.
Oh, even better, I just see you fixed it for me; thanks a lot (sure beats having to clean up after myself ;) )
>> Slightly different question, I have a few cosmetic changes for tc, so which repository to commit this too, is tc-adv to be the gathering point for changes to be considered?
> I've no idea! Recently I tried to merge Toke's repo version into my
> copy of Dave's tc-adv without success. Well the merge works, but
> openwrt complains loudly at this recent version of iproute2 utilities
> and so far it's beyond my wit to tease out how to fix. *if* it worked
> then we could be down to 1 repo, 1 version that worked for linux & openwrt.
At least to me that sounds like a decent strategy, no?
>
> Speaking purely personally, committing to tc-adv would mean openwrt type
> people would test/play with it (me!) Committing to kau.toke.de would
> mean non-openwrters would play....of course you could cherrypick/commit
> to both :-)
Since I only have commit permissions at tc-adv (I am not asking for more) I will just play with the tc-adv repository and hope Jonathan will cherry pick (or even just implement the ideas in his own way) everything he considers worth it…
Best Regards
Sebastian
>
> Kevin
prev parent reply other threads:[~2015-11-01 17:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-31 19:35 Kevin Darbyshire-Bryant
2015-10-31 20:29 ` Dave Taht
2015-11-01 9:47 ` Sebastian Moeller
2015-11-01 13:21 ` Kevin Darbyshire-Bryant
2015-11-01 16:05 ` Sebastian Moeller
2015-11-01 17:18 ` Kevin Darbyshire-Bryant
2015-11-01 17:48 ` Sebastian Moeller [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
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=5E484E77-C716-4703-940B-C3D2F08809B6@gmx.de \
--to=moeller0@gmx.de \
--cc=cake@lists.bufferbloat.net \
--cc=kevin@darbyshire-bryant.me.uk \
/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