Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Martin Zaharinov <micron10@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Bug or not Cake + hfsc or Cake + Drr
Date: Thu, 7 Mar 2019 12:15:14 +0200	[thread overview]
Message-ID: <CALidq=VKHwiMbCR1bidm1xgGVtju6m+VU9Amd7EpEtbMuN+WiQ@mail.gmail.com> (raw)
In-Reply-To: <8736nz11mt.fsf@toke.dk>

[-- Attachment #1: Type: text/plain, Size: 1076 bytes --]

Hi Toke
i have little network with 100 users with ip 192.168.10.0/24

eth0 internet
eth1 lan + pppoe

on pppeo i have network 192.168.11.0/24

now i use hfsc to shape users by services
i have 3 services
1. 5mbit
2. 7mbit
3. 10mbit

with hfsc i use classid to select user and speed but in cake not have
classid support and this is a problem i want to use cake and set to every
users different speed


On Thu, Mar 7, 2019, 11:21 Toke Høiland-Jørgensen <toke@redhat.com> wrote:

> Martin Zaharinov <micron10@gmail.com> writes:
>
> > Hi i try to  make clear shaper with cake and drr
> > in this test i add drr for root and make class to set limit by ip
> > i use kernel 4.9.x and latest sch_cake from github
> >
> > but in dmesg have error:
> >
> > [  609.157445] drr_dequeue: cake qdisc 8004: is non-work-conserving?
> > [  609.212679] drr_dequeue: cake qdisc 8003: is non-work-conserving?
>
> Yeah, you can't use cake as a DRR leaf qdisc. But why would you want to
> do that? Cake contains its own DRR round-robin scheduler...
>
> -Toke
>

[-- Attachment #2: Type: text/html, Size: 1863 bytes --]

  reply	other threads:[~2019-03-07 10:15 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 [this message]
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
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='CALidq=VKHwiMbCR1bidm1xgGVtju6m+VU9Amd7EpEtbMuN+WiQ@mail.gmail.com' \
    --to=micron10@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=toke@redhat.com \
    /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