From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: "codel@lists.bufferbloat.net" <codel@lists.bufferbloat.net>
Subject: Re: [Codel] The next slice of cake
Date: Wed, 1 Apr 2015 22:19:45 -0700 [thread overview]
Message-ID: <CAA93jw5PMcT02D9krx8V7VWj5j2BG4cdfs3dpzM3Xm4oHphTWg@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw7sdziMULjFVmv1T-wdFN=WHDeZkvZVXJQtFPG01a+JTA@mail.gmail.com>
I note the backport to prior to 3.18 is no longer needed at this
point, I have no intentions of going back to a kernel that old.
Does anyone here care about keeping this working with anything older than 3.18?
On Wed, Apr 1, 2015 at 10:17 PM, Dave Taht <dave.taht@gmail.com> wrote:
> On Wed, Apr 1, 2015 at 9:48 PM, Jonathan Morton <chromatix99@gmail.com> wrote:
>>
>>> On 30 Mar, 2015, at 22:28, Dave Taht <dave.taht@gmail.com> wrote:
>>>
>>>> I made a lot of progress over the weekend, and got cake3 running on a sacrificial box today. No crashes yet!
>>>
>>> Preliminary patches always appreciated. I plan to do a build thursday
>>> for a test cycle this weekend of various things.
>>
>> Have a go with this, then. I took the time to do quite a lot of little cleanup things, such as suppressing the statistics output of classes that are not in use.
>>
>> Tests on the Pentium-MMX show similar throughput and latency capabilities to the first version of cake, but this version has more robust behaviour in high-traffic situations - and the Diffserv logic is also far more useful. I’m working towards getting OProfile running on at least one of my desktop-type machines; hopefully it’ll work sufficiently well on the Pentium-MMX, since that’s the easiest one to drive into saturation.
>
> Perf is included in every kernel these days, it is way better than
> oprofile, and easy to build if you are running natively.
> in your linux build dir:
>
> cd tools
> make # to get more info
>
>
>> The kernel patch applies on top of the previous one, but the iproute2 patch should apply to stock. Note that the current git version of iproute2 seems to have a problem with displaying the stats from an ingress filter.
>
> I think for benefit of the audience a fresh patch would be better. I
> will see if this applies on top of my old patches.
>
>>
>> - Jonathan Morton
>>
>
>
>
> --
> Dave Täht
> Let's make wifi fast, less jittery and reliable again!
>
> https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
--
Dave Täht
Let's make wifi fast, less jittery and reliable again!
https://plus.google.com/u/0/107942175615993706558/posts/TVX3o84jjmb
prev parent reply other threads:[~2015-04-02 5:19 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-17 20:08 Jonathan Morton
2015-03-18 7:22 ` Sebastian Moeller
2015-03-18 8:41 ` Jonathan Morton
2015-03-18 10:39 ` Sebastian Moeller
2015-03-18 15:10 ` Kathleen Nichols
2015-03-18 15:20 ` Jonathan Morton
2015-03-18 21:20 ` Dave Taht
2015-03-21 16:09 ` Dave Taht
2015-03-21 23:55 ` Jonathan Morton
2015-03-22 9:39 ` Sebastian Moeller
2015-03-22 10:43 ` Jonathan Morton
2015-03-22 12:51 ` Sebastian Moeller
2015-03-22 15:29 ` Jonathan Morton
2015-03-30 17:28 ` Jonathan Morton
2015-03-30 18:23 ` Sebastian Moeller
2015-03-31 3:22 ` Jonathan Morton
2015-03-31 7:12 ` Sebastian Moeller
2015-03-31 12:47 ` Jonathan Morton
2015-03-30 19:28 ` Dave Taht
2015-04-02 4:48 ` Jonathan Morton
2015-04-02 5:17 ` Dave Taht
2015-04-02 5:19 ` Dave Taht [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/codel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw5PMcT02D9krx8V7VWj5j2BG4cdfs3dpzM3Xm4oHphTWg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=chromatix99@gmail.com \
--cc=codel@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