From: Dave Taht <dave.taht@gmail.com>
To: cake@lists.bufferbloat.net, Jesper Dangaard Brouer <brouer@redhat.com>
Subject: [Cake] the meta problem of memory, locks, and multiple cpus
Date: Thu, 29 Oct 2015 10:08:34 +0100 [thread overview]
Message-ID: <CAA93jw4KoFanpVWCAy1kMbC1-yLp2GZKknufe1APD0A17jQ40Q@mail.gmail.com> (raw)
The real problem A) that I wish we could solve at the qdisc layer
is that we could size everything more appropriately if we actually
*knew* the physical link rate in many cases. It is *right there* in
the sys filesystem for ethernet devices, if only there was some way to
get at it, and get notifications if it changed.... or merely to know
the underlying operating range of the device at qdisc init time. It is
dumb to allow 50MB of memory for a 10mbit device just to make the
10GigE folk happy.
yes, I know this does not help on stacked qdiscs, but...
the other meta problem is getting to where we can outperform mq + cake
somehow on a cpu basis - I dislike intensely the 8 hardware and BQL
queues in the mvneta driver and elsewhere, they totally clobber
latency.
If there was some sort of saner locking structure that would instead
let us repurpose those 8 hardware queues to be QoS only and let us let
cake get run on multiple cpus in those cases.....
bringing jesper back in...
Dave Täht
I just invested five years of my life to making wifi better. And,
now... the FCC wants to make my work, illegal for people to install.
https://www.gofundme.com/savewifi
next reply other threads:[~2015-10-29 9:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-29 9:08 Dave Taht [this message]
2015-10-29 11:00 ` Jesper Dangaard Brouer
2015-11-03 0:55 ` Stephen Hemminger
2015-11-03 1:32 ` Jonathan Morton
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=CAA93jw4KoFanpVWCAy1kMbC1-yLp2GZKknufe1APD0A17jQ40Q@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=brouer@redhat.com \
--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