From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Dave Taht <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] wash option not in tc-adv
Date: Mon, 30 Nov 2015 12:09:38 +0000 [thread overview]
Message-ID: <565C3C82.5060600@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <CAA93jw6g0TJF1zGph+7goSP-KNwaC2x4W86YzP-Oizz+11VkAw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 861 bytes --]
On 30/11/15 11:36, Dave Taht wrote:
> yes, you typically do have to install (or re-install) tc-adv with the
>
> opkg install --force-overwrite tc-adv
I've not hit that problem 'cos I always chicken out and flash the entire
upgrade image :-)
>
> option. The ongoing goal of course is to get this stuff mainlined,
> which we seem no closer to doing. I'd really hoped to get some good
> performance numbers back this past weekend, and didn't. I do "feel"
> that the revised codel model is not testing out as good as the one in
> fq_codel, that on a variety of tests set associative hashing is not
> seemingly worth it...
So is the code wrong, or the coding of the tests? ;-)
>
> and boy, oh boy, does peeling have issues on the hardware I tried it on.
So does this mean you managed to bring back your Archer from its coma?
Hoping yes!
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4816 bytes --]
next prev parent reply other threads:[~2015-11-30 12:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-29 22:59 Vincent Frentzel
2015-11-30 6:41 ` Vincent Frentzel
2015-11-30 10:10 ` Kevin Darbyshire-Bryant
2015-11-30 10:22 ` Vincent Frentzel
2015-11-30 11:22 ` Kevin Darbyshire-Bryant
2015-11-30 11:31 ` Kevin Darbyshire-Bryant
2015-11-30 11:36 ` Dave Taht
2015-11-30 12:09 ` Kevin Darbyshire-Bryant [this message]
2015-11-30 21:15 ` Vincent Frentzel
2015-11-30 21:49 ` Kevin Darbyshire-Bryant
2015-12-01 0:18 ` Toke Høiland-Jørgensen
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=565C3C82.5060600@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@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