Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@redhat.com>
To: Martin Zaharinov <micron10@gmail.com>, Pete Heist <pete@heistp.net>
Cc: "Toke Høiland-Jørgensen via Cake" <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Bug or not Cake + hfsc or Cake + Drr
Date: Thu, 07 Mar 2019 19:28:23 +0100	[thread overview]
Message-ID: <875zsu1quw.fsf@toke.dk> (raw)
In-Reply-To: <CALidq=WGzNBnjR5iH7hJ0my_UAzNmnL+xe3Mpf+JUkjXeYqoDw@mail.gmail.com>

Martin Zaharinov <micron10@gmail.com> writes:

> Hi Pete
> yes i find this patch and add to cake source
> and in my test with hfsc and cake
> i use
>
> tc qdisc add dev eth1 root handle 1: hfsc default 1
> tc class add dev eth1 parent 1: classid 1:1 hfsc ls rate 7mbit ul rate 7mbit
> tc qdisc add dev eth1 parent 1:1 cake besteffort bandwidth 5mbit datacentre
> nat memlimit 32m
>
> user speed is 5mbit and on hfsc i add extra 2 mbit to give free limit for
> cake.
> and work fine but in dmesg get :
>
> [44835.530255] qdisc_peek_len: cake qdisc 8017: is non-work-conserving?
> [44840.689403] HFSC: cake qdisc 8012: is non-work-conserving?

Yes. As I said, you *cannot use the cake shaper* when running in under
HFSC.

> user receive 5mbit for upload and download and fine work.
> mai be need to add no-split-gso to config
>
> but after add have same error on dmesg :
>
> [44955.641391] HFSC: cake qdisc 8021: is non-work-conserving?
> [44955.958904] HFSC: cake qdisc 801C: is non-work-conserving?
>
> but work fine and will remove warrning from kernel source to not list in
> dmesg :)

I very much doubt that things will just continue to "work fine" if you
just remove the warning...

-Toke

  reply	other threads:[~2019-03-07 18:28 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-07  6:35 Martin Zaharinov
2019-03-07  9:20 ` Toke Høiland-Jørgensen
2019-03-07 10:15   ` Martin Zaharinov
2019-03-07 10:30     ` Toke Høiland-Jørgensen
2019-03-07 10:41       ` Martin Zaharinov
2019-03-07 10:44         ` Martin Zaharinov
2019-03-07 10:46         ` Toke Høiland-Jørgensen
     [not found]           ` <CALidq=UWmK4ROWbu9p-70xUON=ws=CPEs=Br=2FNHudbomKkLQ@mail.gmail.com>
2019-03-07 11:05             ` Toke Høiland-Jørgensen
2019-03-07 11:07               ` Martin Zaharinov
2019-03-07 11:25                 ` Toke Høiland-Jørgensen
2019-03-07 11:32                   ` Martin Zaharinov
2019-03-07 18:05                     ` Pete Heist
2019-03-07 18:23                       ` Martin Zaharinov
2019-03-07 18:28                         ` Toke Høiland-Jørgensen [this message]
2019-03-07 18:31                           ` Martin Zaharinov
2019-03-07 18:40                             ` Toke Høiland-Jørgensen
2019-03-07 23:59                         ` 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=875zsu1quw.fsf@toke.dk \
    --to=toke@redhat.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=micron10@gmail.com \
    --cc=pete@heistp.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