Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: "Toke Høiland-Jørgensen" <toke@redhat.com>
Cc: bloat@lists.bufferbloat.net, cake@lists.bufferbloat.net
Subject: Re: [Cake] Fwd: Re: Unable to create htb tc classes more than 64K
Date: Tue, 27 Aug 2019 16:04:09 -0400	[thread overview]
Message-ID: <20190827160409.3c1afcc2@xps13> (raw)
In-Reply-To: <87h864l6q5.fsf@toke.dk>

On Mon, 26 Aug 2019 09:35:14 +0200
Toke Høiland-Jørgensen <toke@redhat.com> wrote:

> Turns out that with the "earliest departure time" support in sched_fq,
> it is now possible to write a shaper in eBPF, thus avoiding the global
> qdisc lock in sched_htb. This is pretty cool, if you ask me! :)
> 
> -Toke
> 

Thanks, I may use this to revisit doing netem in eBPF (xnetem).
Not having this feature was a show stopper at the time.

      reply	other threads:[~2019-08-27 20:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9cbefe10-b172-ae2a-0ac7-d972468eb7a2@gmail.com>
2019-08-26  7:35 ` Toke Høiland-Jørgensen
2019-08-27 20:04   ` Stephen Hemminger [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=20190827160409.3c1afcc2@xps13 \
    --to=stephen@networkplumber.org \
    --cc=bloat@lists.bufferbloat.net \
    --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