Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Pete Heist <pete@heistp.net>
To: Martin Zaharinov <micron10@gmail.com>
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, 7 Mar 2019 19:05:32 +0100	[thread overview]
Message-ID: <FBF542E2-5F4A-42AE-A1F5-3A8162A493D6@heistp.net> (raw)
In-Reply-To: <CALidq=W2R=ueOMA4u1pp+taNhM9DWRYxam79=pSL8Q52DO7RPQ@mail.gmail.com>

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

If it’s just straight cake under hfsc with a rate here’s what I do (obviously replace 100mbit with your rate):

tc qdisc add dev eth1 root handle 1: hfsc default 1
tc class add dev eth1 parent 1: classid 1:1 hfsc ls rate 100mbit ul rate 100mbit
tc qdisc add dev eth1 parent 1:1 cake

Also, there were recent fixes to the Linux kernel and cake regarding GSO splitting. You may find with hfsc on older kernels that you have to use “cake no-split-gso” to avoid lockups.

> On Mar 7, 2019, at 12:32 PM, Martin Zaharinov <micron10@gmail.com> wrote:
> 
> thanks i will try
> 
> 
> 
> On Thu, Mar 7, 2019, 13:25 Toke Høiland-Jørgensen <toke@redhat.com <mailto:toke@redhat.com>> wrote:
> Martin Zaharinov <micron10@gmail.com <mailto:micron10@gmail.com>> writes:
> 
> > please write my one sample line with this
> 
> From your script you'd need to use:
> 
> tc qdisc add dev eth1 parent 1:0004 cake
> 
> instead of
> 
> tc qdisc add dev eth1 parent 1:0004 sfq perturb 10
> 
> And adjust your HFSC parameter to shape to the rate you want. Can't help
> you with that part, sorry, you'll need to go read up on shaping with
> HFSC (or I'd suggest maybe using HTB instead as that is simpler to
> configure). There are loads of tutorials for that online :)
> 
> -Toke
> _______________________________________________
> Cake mailing list
> Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake


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

  reply	other threads:[~2019-03-07 18:05 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 [this message]
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=FBF542E2-5F4A-42AE-A1F5-3A8162A493D6@heistp.net \
    --to=pete@heistp.net \
    --cc=cake@lists.bufferbloat.net \
    --cc=micron10@gmail.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