From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] Playing with ingredients = ruined the CAKE
Date: Sun, 31 May 2020 17:08:16 +0000 [thread overview]
Message-ID: <7D02924D-1B16-4274-8BBF-6CBAA59CBB59@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <CAJnXXogEindF=KvVOZUVa1VeZGDVA8hCNfaBAmh6HkJ_sjwPZg@mail.gmail.com>
> On 31 May 2020, at 17:38, John Yates <john@yates-sheets.org> wrote:
>
> Kevin,
>
> I am curious how this effort relates to Dave Taht's point in his May
> 20th "not really huge on EF landing where it does in wifi" thread.
>
> /john
Hi John,
I have absolutely no idea, don’t appear to have that thread :-) My own DSCP/CAKE interests are aligned to exercising CAKE’s built-in classification/bandwidth allocations across my WAN link. In essence I have traffic types of ‘Least Effort’ (bittorrent - nearly starvable), ‘Bulk’ (backups/long term up/downloads - low minimum b/w), ’Normal’ (Most short term stuff - all bandwith), VI (video conference calls/streaming, long-term more important flows latency important- up to 1/2 b/w), VO (voice/latency critical up to 1/4 b/w). Or two levels of ’not so important’ and two levels of ‘more important’ around normal/everything.
The classification process happens as a combination of iptables/ipsets rules on the internet router using tc act_ctinfo to preserve the DSCP classification of flows across the WAN.
Cheers,
Kevin D-B
gpg: 012C ACB2 28C6 C53E 9775 9123 B3A2 389B 9DE2 334A
next prev parent reply other threads:[~2020-05-31 17:08 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-29 10:06 Kevin Darbyshire-Bryant
2020-05-29 15:24 ` Kevin Darbyshire-Bryant
2020-05-31 10:04 ` Kevin Darbyshire-Bryant
2020-05-31 16:38 ` John Yates
2020-05-31 17:08 ` Kevin Darbyshire-Bryant [this message]
2020-05-31 17:26 ` John Yates
2020-05-31 18:08 ` Kevin Darbyshire-Bryant
2020-05-31 19:01 ` Dave Taht
2020-05-31 19:25 ` 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=7D02924D-1B16-4274-8BBF-6CBAA59CBB59@darbyshire-bryant.me.uk \
--to=kevin@darbyshire-bryant.me.uk \
--cc=cake@lists.bufferbloat.net \
/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