From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Dave Taht <dave.taht@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] diffserv in cake
Date: Fri, 30 Oct 2015 13:32:13 +0100 [thread overview]
Message-ID: <87mvv0edv6.fsf@toke.dk> (raw)
In-Reply-To: <CAA93jw7LEsR96bm60-61onGEQZkxu-m8zC_7QY49Qv=7SC6xsg@mail.gmail.com> (Dave Taht's message of "Fri, 30 Oct 2015 08:13:47 -0400")
Dave Taht <dave.taht@gmail.com> writes:
> It was my hope, instead, that with ease we could add new models for
> how to handle diffserv handling along existing htb based schemes.
Uh, I know: Let's allow the user to install a custom BPF filter that
classifies packets into classes... </sarcasm>
I'd say we either pick one, or allow arbitrary classification with tc
filter. In my book, the diffserv4 that mirrors 802.11e is a fine choice :)
-Toke
next prev parent reply other threads:[~2015-10-30 12:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-30 12:13 Dave Taht
2015-10-30 12:32 ` Toke Høiland-Jørgensen [this message]
[not found] ` <5A86B264-B957-41D2-9E4C-D1F9C525A99F@gmx.de>
[not found] ` <CAA93jw4xv-PLtAnw96xQmJoRFZmd24fJq04BJnc4_NPTPH2LqA@mail.gmail.com>
2015-10-30 12:40 ` Sebastian Moeller
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=87mvv0edv6.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cake@lists.bufferbloat.net \
--cc=dave.taht@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