From: Dave Taht <dave.taht@gmail.com>
To: cake@lists.bufferbloat.net
Subject: [Cake] delayed bql and/or ethernet devices with alternate settings
Date: Sun, 12 Apr 2015 15:13:10 -0700 [thread overview]
Message-ID: <CAA93jw66_cSrVN+5mboJR2RRS6i0Xu88gJgW3EUt9MoKEx=wMA@mail.gmail.com> (raw)
We actually need not do the bandwidth shaping in the qdisc.
IF an ethernet device existed that let you program in
its rate to not be line rate, that would be a nice feature,
then all the existing mechanisms (like BQL) would "just work"
and we would need no software rate shaping in that case.
So, despite transmitting a packet at 1gbit, returning an completion
interrupt as if it was transmitting at a a user specified 20 (or
X)mbit, would work with all the higher mechanisms in the kernel.
(I keep hoping, undocumented, somewhere in every ethernet
device, is a configuration option like this)
Receive is harder, you still have to drain the rx ring at
line rate.
--
Dave Täht
Open Networking needs **Open Source Hardware**
https://plus.google.com/u/0/+EricRaymond/posts/JqxCe2pFr67
reply other threads:[~2015-04-12 22:13 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAA93jw66_cSrVN+5mboJR2RRS6i0Xu88gJgW3EUt9MoKEx=wMA@mail.gmail.com' \
--to=dave.taht@gmail.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