Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Jonathan Morton <chromatix99@gmail.com>
To: Sebastian Moeller <moeller0@gmx.de>
Cc: Cake List <cake@lists.bufferbloat.net>, dcaratti@redhat.com
Subject: Re: [Cake] [PATCH net-next 1/5] sch_cake: fix IP protocol handling in the presence of VLAN tags
Date: Fri, 26 Jun 2020 19:36:04 +0300	[thread overview]
Message-ID: <8BAD586F-43FB-4ED1-865E-45AFB9AE9D95@gmail.com> (raw)
In-Reply-To: <E6DDAA1E-E7E9-47D2-8616-20B7AADF015A@gmx.de>

> On 26 Jun, 2020, at 5:59 pm, Sebastian Moeller <moeller0@gmx.de> wrote:
> 
> thinking this over, I wonder whether a hypothetical carrier grade cake, might not actually grow a classify-by-vlan-priority keyword to allow switching over to using VLAN priority tags instead of dscps? That would avoid tempting carriers to re-map deeep-encapsulated dscps if they can just ignore them for good. And it scratches my pet itch, that 3 bits of classification should be enough for >80 % of the cases ;)
> 
> What do you think?

If carriers could use Ethernet VLANs for internal purposes instead of DSCPs, I would count that as progress towards allowing DSCPs to carry end-to-end information.  And if there's a desire for a software qdisc which fits that paradigm, then we can do a requirements analysis which might well lead to something useful being developed.

But that isn't going to be Cake.  It'll be a different qdisc which might share some features and technology with Cake, but definitely arranged in a different order and with a different focus.

 - Jonathan Morton

  reply	other threads:[~2020-06-26 16:36 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-25 11:55 [Cake] [PATCH net-next 0/5] sched: A series of fixes and optimisations for sch_cake Toke Høiland-Jørgensen
2020-06-25 11:55 ` [Cake] [PATCH net-next 1/5] sch_cake: fix IP protocol handling in the presence of VLAN tags Toke Høiland-Jørgensen
2020-06-25 19:29   ` David Miller
2020-06-25 19:53     ` Toke Høiland-Jørgensen
2020-06-25 20:00       ` David Miller
2020-06-26  8:27       ` Davide Caratti
2020-06-26 12:52         ` Toke Høiland-Jørgensen
2020-06-26 14:01           ` Jamal Hadi Salim
2020-06-26 18:52           ` Davide Caratti
2020-06-29 10:27             ` Toke Høiland-Jørgensen
2020-06-26 13:11         ` Jonathan Morton
2020-06-26 14:59           ` Sebastian Moeller
2020-06-26 16:36             ` Jonathan Morton [this message]
2020-06-26 22:00           ` Stephen Hemminger
2020-06-25 11:55 ` [Cake] [PATCH net-next 2/5] sch_cake: don't try to reallocate or unshare skb unconditionally Toke Høiland-Jørgensen
2020-06-25 11:55 ` [Cake] [PATCH net-next 3/5] sch_cake: don't call diffserv parsing code when it is not needed Toke Høiland-Jørgensen
2020-06-25 11:55 ` [Cake] [PATCH net-next 4/5] sch_cake: add RFC 8622 LE PHB support to CAKE diffserv handling Toke Høiland-Jørgensen
2020-06-25 11:55 ` [Cake] [PATCH net-next 5/5] sch_cake: fix a few style nits Toke Høiland-Jørgensen
2020-06-25 19:31 ` [Cake] [PATCH net-next 0/5] sched: A series of fixes and optimisations for sch_cake David Miller
2020-06-25 19:49   ` Toke Høiland-Jørgensen

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=8BAD586F-43FB-4ED1-865E-45AFB9AE9D95@gmail.com \
    --to=chromatix99@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=dcaratti@redhat.com \
    --cc=moeller0@gmx.de \
    /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