Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Dave Taht <dave.taht@gmail.com>, Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] DSCP ramblings
Date: Thu, 23 Apr 2020 10:50:33 +0000	[thread overview]
Message-ID: <62FFBC75-51F0-4527-A64D-3C379D3E18D9@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <20200422094428.2ee29433@hermes.lan>

[-- Attachment #1: Type: text/plain, Size: 2439 bytes --]



> On 22 Apr 2020, at 17:44, Stephen Hemminger <stephen@networkplumber.org> wrote:
> 
> In my experience, except for a small number of cases (RDMA etc) Diffserv is a
> complete waste of time. There is no global ordering, there is no guarantee against
> starvation and any sane ISP strips the bits off or ignores them.
> 
> Diffserv is even an issue at scale in the cloud. What does DSCP mean exactly on
> outer headers, who gets to decide for which service. And what about inner headers
> and propogating inner to outer. Its a mess.

That’s…depressing :-/ And suggests there are at least 6 bits spare in the ’TOS’ byte, perhaps that should go forward at the next IETF meeting ;-)

In my own naive home network fiefdom I would like to have some level of control as to who/what gets the lion’s/fairshare of my ISP wan link.  I don’t actually care whether that DSCP decision makes it/returns on the wan link…I have my own combination of tc act_ctinfo (in upstream linux) and ‘iptables connmark —setdscp’ (not in upstream linux yet) to do my DSCP mark saving/restoration, so what I set sticks and affects CAKE’s tin allocation & shaping decisions.  I want my wife’s facetime call to her sister to work perfectly, I want my bittorrenting to sit there in the background unnoticed, I want my network backup job/s to run in good time but not at the expense of interactive web browsing, ssh’ing etc.  I want my BBC iplayer radio to sit there streaming away at the best quality, no interruptions.  It’s all possible.

As it currently stands I’ve a series of guestimate iptables rules mainly based on source or destination ip address (occasionally a bit of port number) but that’s pretty coarse.  Why can’t the application do it?

LE - Least Effort - 0/16 can be starved - bittorrent
GE - Good Effort - 1/16 not starved - background downloads, windows update
BE - Best Effort - 16/16 Normal activity, default
SP - Streaming Priority - 8/16 high bitrate streaming, Video/Audio streaming,  Video portion of video conferencing
IIP - Interactive/Important Priority - 4/16 low bitrate streaming, SIP/VOIP, interactive SSH, DNS, Audio portion of video conferencing

I’m still stunned/shocked by the lack of obvious DSCP support in libcurl.  If DSCP setting isn’t easy to do, no one will do it.  Perhaps if it is built, people will come?

I’m probably stupid.  And now depressed!

Kevin

[-- Attachment #2: Message signed with OpenPGP --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  parent reply	other threads:[~2020-04-23 10:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-22 15:58 Kevin Darbyshire-Bryant
2020-04-22 16:15 ` Dave Taht
2020-04-22 16:20   ` Dave Taht
2020-04-22 16:44     ` Stephen Hemminger
2020-04-22 16:58       ` Dave Taht
2020-04-23 10:50       ` Kevin Darbyshire-Bryant [this message]
2020-04-22 17:17     ` Kevin Darbyshire-Bryant
2020-04-22 17:45       ` Dave Taht

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=62FFBC75-51F0-4527-A64D-3C379D3E18D9@darbyshire-bryant.me.uk \
    --to=kevin@darbyshire-bryant.me.uk \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=stephen@networkplumber.org \
    /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