Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Jonathan Morton <chromatix99@gmail.com>,
	dagofthedofg@gmail.com,  Cake List <Cake@lists.bufferbloat.net>
Subject: Re: [Cake] Multiple Hardware Queues
Date: Sun, 15 Jul 2018 08:57:23 -0700	[thread overview]
Message-ID: <CAA93jw6s4j8QccXtAxyMA=HZQ+guKvVxBiwzevm-O1r4QwfnHQ@mail.gmail.com> (raw)
In-Reply-To: <87o9f895ei.fsf@toke.dk>

I note that I like the idea of cake-mq (or rather, cake-smp). If we
can currently achieve 50gbit bottlenecking on one cpu, what can be
done to get past 100gbit?

tc qdisc add dev eth root cake-smp bandwidth 100gbit

has a nice ring to it don't you think? :)

* BQL's estimator is essentially additive. If you have 64 hw queues
(common in 10gige hw), you've got a ton of inessential latency that
builds up there due to bulking.

* I have grave doubts about 64k aqm'd queues at any speed. Better to
have less queues.

* In a naive parallel implementation (and excluding some painful
implementation details) - only the global shaped bandwidth limit has a
need for atomic, cross cpu access, and even that can essentially be
rcu'd.

  reply	other threads:[~2018-07-15 15:57 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-15  7:41 dag dg
2018-07-15  8:10 ` Jonathan Morton
2018-07-15 10:09   ` Toke Høiland-Jørgensen
2018-07-15 15:57     ` Dave Taht [this message]
2018-07-15 20:28       ` Toke Høiland-Jørgensen
2018-07-16 19:03         ` dag dg
2018-07-16 19:27           ` Georgios Amanakis

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='CAA93jw6s4j8QccXtAxyMA=HZQ+guKvVxBiwzevm-O1r4QwfnHQ@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=Cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    --cc=dagofthedofg@gmail.com \
    --cc=toke@toke.dk \
    /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