From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: cake@lists.bufferbloat.net, Jesper Dangaard Brouer <brouer@redhat.com>
Subject: Re: [Cake] Announce - possible new feature - DSCP cleaning
Date: Wed, 18 Nov 2015 18:56:39 +0000 [thread overview]
Message-ID: <564CC9E7.7060104@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <87oaera5a8.fsf@toke.dk>
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
On 18/11/15 11:57, Toke Høiland-Jørgensen wrote:
> Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk> writes:
>
>> The jury hasn't even been assembled, let alone sat as to whether these
>> (potentially) increasing targets/intervals on 'slow' links is a good
>> thing(tm) or not.
> I think I was leaning towards 'no' last time around on this.
That may be, and my gut & head goes with 'no' as well. Unfortunately I
failed spectacularly to produce a suitable test. Also I got somewhat
fed up with recompiling, flashing, rebooting, copying modules with
different tweaks in them, testing again, forgetting where I was etc
etc. To that end I'm working on a way to pass 'copy target', 'copy
interval' etc type flags so that with a simple tc command I can turn the
copying of parameters from tin[0] across...or not.
The task of producing a suitable test will still remain!
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4816 bytes --]
next prev parent reply other threads:[~2015-11-18 18:56 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-17 19:05 Dave Taht
2015-11-18 11:17 ` Kevin Darbyshire-Bryant
2015-11-18 11:57 ` Toke Høiland-Jørgensen
2015-11-18 18:56 ` Kevin Darbyshire-Bryant [this message]
-- strict thread matches above, loose matches on Subject: below --
2015-11-10 15:00 Kevin Darbyshire-Bryant
2015-11-16 14:59 ` Kevin Darbyshire-Bryant
2015-11-16 15:03 ` Dave Taht
2015-11-16 15:20 ` Kevin Darbyshire-Bryant
2015-11-16 15:57 ` Dave Taht
2015-11-16 16:25 ` Kevin Darbyshire-Bryant
2015-11-16 17:47 ` Kevin Darbyshire-Bryant
2015-11-16 17:59 ` Dave Taht
2015-11-16 18:11 ` Kevin Darbyshire-Bryant
2015-11-16 18:25 ` Dave Taht
2015-11-16 18:32 ` Sebastian Moeller
2015-11-16 18:35 ` Dave Taht
2015-11-16 18:43 ` Kevin Darbyshire-Bryant
2015-11-16 18:47 ` Dave Taht
2015-11-16 20:09 ` Kevin Darbyshire-Bryant
2015-11-17 10:12 ` Dave Taht
2015-11-17 18:52 ` Kevin Darbyshire-Bryant
2015-11-16 15:33 ` 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=564CC9E7.7060104@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=brouer@redhat.com \
--cc=cake@lists.bufferbloat.net \
--cc=toke@toke.dk \
/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