From: Jonathan Morton <chromatix99@gmail.com>
To: Adrian Popescu <adriannnpopescu@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@redhat.com>,
"Cake List" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] profiling using perf
Date: Mon, 11 Mar 2019 17:53:40 +0200 [thread overview]
Message-ID: <5CBE005F-62B8-41F0-9EB9-7EE80ADF6674@gmail.com> (raw)
In-Reply-To: <CAF3M4P2WeHWPH+Ax8Eoy81t2mTEg1znPxK3R=Rzy4BpV+SX9tQ@mail.gmail.com>
> On 11 Mar, 2019, at 4:49 pm, Adrian Popescu <adriannnpopescu@gmail.com> wrote:
>
> This doesn't mean cake is poorly optimized or poorly
> implemented. It's not a good fit for small embedded systems with small
> CPU caches.
More importantly, how much CPU time is spent elsewhere than in sch_cake.c? I suspect there's a lot of overhead that we have only indirect control over.
- Jonathan Morton
prev parent reply other threads:[~2019-03-11 15:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 20:58 Georgios Amanakis
2019-03-08 21:01 ` Georgios Amanakis
2019-03-09 16:03 ` Toke Høiland-Jørgensen
2019-03-11 14:49 ` Adrian Popescu
2019-03-11 15:53 ` Jonathan Morton [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=5CBE005F-62B8-41F0-9EB9-7EE80ADF6674@gmail.com \
--to=chromatix99@gmail.com \
--cc=adriannnpopescu@gmail.com \
--cc=cake@lists.bufferbloat.net \
--cc=toke@redhat.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