From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] tc coding comments
Date: Thu, 19 Nov 2015 12:15:59 +0100 [thread overview]
Message-ID: <87io4y8ck0.fsf@toke.dk> (raw)
In-Reply-To: <564DAE6D.1090203@darbyshire-bryant.me.uk> (Kevin Darbyshire-Bryant's message of "Thu, 19 Nov 2015 11:11:41 +0000")
Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> writes:
> There's an obvious enhancement here too: Specify egress dscp code per
> tin.
I think that is opening a whole 'nother can of configuration complexity
worms that we are better off steering clear of. Especially if they are
to be implemented as regular tc options; we already have way too many of
those.
-Toke
next prev parent reply other threads:[~2015-11-19 11:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-19 8:56 Dave Taht
2015-11-19 11:03 ` Sebastian Moeller
2015-11-19 11:11 ` Kevin Darbyshire-Bryant
2015-11-19 11:15 ` Toke Høiland-Jørgensen [this message]
2015-11-19 11:25 ` Kevin Darbyshire-Bryant
2015-11-19 12:05 ` Kevin Darbyshire-Bryant
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=87io4y8ck0.fsf@toke.dk \
--to=toke@toke.dk \
--cc=cake@lists.bufferbloat.net \
--cc=kevin@darbyshire-bryant.me.uk \
/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