Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: dag dg <dagofthedofg@gmail.com>
To: Cake@lists.bufferbloat.net
Subject: [Cake] Multiple Hardware Queues
Date: Sun, 15 Jul 2018 02:41:21 -0500	[thread overview]
Message-ID: <CAO2Qn5nF432bL7R1bNiQ2+o1D6UvB5ytx2MML5NtihHQc+zoFg@mail.gmail.com> (raw)

Firstly let me give my congratulations to the contributors of the Cake
project for Cake being accepted upstream. I've been following the
project for awhile and greatly appreciate the effort that has been put
into it.

Ironically I just wrapped up throwing some unofficial packages
together for Fedora 28 to enable cake support; having it upstream will
make updates a lot easier.

Now that I have cake available and running I just wanted to do one
final check on a technical consideration I had brought up on the
bufferbloat list a few months back, before I lay this notion to rest.

Toke gave me some guidance at that time which helped point me towards
cake. Now that I have it running I wanted to check in one last time to
see if there's any beneficial way I can use cake with multiple
hardware queues or if I need to just give up the chase.

In my box I have acting as a router I have an Intel i350-t2v2 nic that
has two gigabit ports(uplink/local). This card and its corresponding
driver supports multiple hardware-based transmit and receive queues
depending on the number of cores the system has up to 8.

without cake:
qdisc mq 0: dev enp2s0f0 root
qdisc fq_codel 0: dev enp2s0f0 parent :8 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f0 parent :7 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f0 parent :6 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f0 parent :5 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f0 parent :4 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f0 parent :3 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f0 parent :2 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f0 parent :1 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc mq 0: dev enp2s0f1 root
qdisc fq_codel 0: dev enp2s0f1 parent :8 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f1 parent :7 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f1 parent :6 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f1 parent :5 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f1 parent :4 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f1 parent :3 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f1 parent :2 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f1 parent :1 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn

with cake via sqm:
qdisc cake 802c: dev enp2s0f0 root refcnt 9 bandwidth 23Mbit diffserv3
triple-isolate split-gso rtt 100.0ms raw overhead 0
qdisc ingress ffff: dev enp2s0f0 parent ffff:fff1 ----------------
qdisc mq 0: dev enp2s0f1 root
qdisc fq_codel 0: dev enp2s0f1 parent :8 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f1 parent :7 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f1 parent :6 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f1 parent :5 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f1 parent :4 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f1 parent :3 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f1 parent :2 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev enp2s0f1 parent :1 limit 10240p flows 1024
quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc fq_codel 0: dev tun0 root refcnt 2 limit 10240p flows 1024
quantum 1500 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
qdisc cake 802d: dev ifb4enp2s0f0 root refcnt 2 bandwidth 330Mbit
besteffort triple-isolate wash split-gso rtt 100.0ms raw overhead 0

Let me be clear that with cake and sqm I am seeing great results on
the dslreports speed test(A+) so this inquiry is less about solving a
problem and more along the lines of trying to take full advantage of
my available hardware. Any insight would be appreciated, and thanks
again for your contributions.

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

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-15  7:41 dag dg [this message]
2018-07-15  8:10 ` Jonathan Morton
2018-07-15 10:09   ` Toke Høiland-Jørgensen
2018-07-15 15:57     ` Dave Taht
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=CAO2Qn5nF432bL7R1bNiQ2+o1D6UvB5ytx2MML5NtihHQc+zoFg@mail.gmail.com \
    --to=dagofthedofg@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