From: Georgios Amanakis <gamanakis@gmail.com>
To: dag dg <dagofthedofg@gmail.com>
Cc: "Toke Høiland-Jørgensen" <toke@toke.dk>,
"Cake List" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Multiple Hardware Queues
Date: Mon, 16 Jul 2018 15:27:47 -0400 [thread overview]
Message-ID: <CACvFP_iZOzAFB-iaS+uZ3eT4UzBqgFGtsr1zQCxNgN+U1_q1gA@mail.gmail.com> (raw)
In-Reply-To: <CAO2Qn5ko1ceW70m9CuvCcQan50MuXaG01cScAR_SfXNSv-67eQ@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3594 bytes --]
The docsis option shows up in TC qdisc show as: noatm overhead 18 mpu 64.
So I think you are ok.
On Mon, Jul 16, 2018, 3:03 PM dag dg <dagofthedofg@gmail.com> wrote:
> (sorry for the spam Toke, still getting used to a new email client)
>
> Thanks for the input, this is pretty much the info I was hoping for.
> At this point I'll probably swap out the dual port NIC I have with
> something more reasonable and put the i350 to work where its
> performance will actually be used.
>
> Really excited to have cake support in upstream.
>
> Looking at usage I noticed there were a few cake configuration
> parameters I may have missed when setting up my sqm-scripts config.
> Right now I'm just using the "piece-of-cake.qos" example, with my
> interface config file as:
>
> # Uplink and Downlink values are in kbps
> UPLINK=23000
> DOWNLINK=330000
>
> # SQM recipe to use. For more information, see /usr/lib/sqm/*.help
> SCRIPT=piece_of_cake.qos
>
> # Optional/advanced config
>
> #ENABLED=1
> #QDISC=cake
>
> #LLAM=tc_stab
> #LINKLAYER=none
> #OVERHEAD=0
> #STAB_MTU=2047
> #STAB_TSIZE=512
> #STAB_MPU=0
>
> #ILIMIT=
> #ELIMIT=
> #ITARGET=
> #ETARGET=
>
> # ECN ingress resp. egress. Values are ECN or NOECN.
> #IECN=ECN
> #EECN=ECN
>
> # Extra qdisc options ingress resp. egress
> IQDISC_OPTS="nat docsis ingress"
> EQDISC_OPTS="nat docsis ack-filter"
>
> # CoDel target
> #TARGET=5ms
>
> #ZERO_DSCP_INGRESS=1
> #IGNORE_DSCP_INGRESS=1
>
> With the result being:
>
> qdisc noqueue 0: dev lo root refcnt 2
> qdisc fq_codel 0: dev enp6s0 root refcnt 2 limit 10240p flows 1024
> quantum 1514 target 5.0ms interval 100.0ms memory_limit 32Mb ecn
> qdisc cake 803b: dev enp2s0f0 root refcnt 9 bandwidth 23Mbit
> besteffort triple-isolate nat ack-filter split-gso rtt 100.0ms noatm
> overhead 18 mpu 64
> 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 803c: dev ifb4enp2s0f0 root refcnt 2 bandwidth 330Mbit
> besteffort triple-isolate nat wash ingress split-gso rtt 100.0ms noatm
> overhead 18 mpu 64
>
> I don't fully understand the docsis option, is it supposed to show up
> under the tc qdisc show or is it all in the background? I'm just
> worried I'm not setting this up properly.
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake
>
[-- Attachment #2: Type: text/html, Size: 4359 bytes --]
prev parent reply other threads:[~2018-07-16 19:27 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
2018-07-15 20:28 ` Toke Høiland-Jørgensen
2018-07-16 19:03 ` dag dg
2018-07-16 19:27 ` Georgios Amanakis [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=CACvFP_iZOzAFB-iaS+uZ3eT4UzBqgFGtsr1zQCxNgN+U1_q1gA@mail.gmail.com \
--to=gamanakis@gmail.com \
--cc=cake@lists.bufferbloat.net \
--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