Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: Cake List <cake@lists.bufferbloat.net>
Subject: [Cake] Playing with ingredients = ruined the CAKE
Date: Fri, 29 May 2020 10:06:50 +0000	[thread overview]
Message-ID: <5136DAB5-B975-4D36-948D-A5A4167A8FC7@darbyshire-bryant.me.uk> (raw)

I’m trying to create a ‘diffserv5’ for the purposes of implementing a 'Least Effort’ class: something like LE=Bittorrent, BK=Backups/long term down/uploads, BE=Best Effort/Normal, VI=Streaming media/facetime/zoom, VO=VOIP/SIP.  Not too hard you’d think, take diffserv4 and add a tin.

I did this with tin allocation: 0=LE, 1=BE, 2=BK, 3=VI, 4=VO.  BW allocation relative to base rate = LE>>8, BE>>0, BK>>4, VI>>1, VO>>2.  Tin display order = 0, 2, 1, 3, 4.  In theory I don’t mind LE being starved hence the above order.  This pretty much ‘jammed' the shaper as soon as any traffic went into LE with other higher priority tins seeing huge latencies, lots of drops and general bad news all over.

I tried again with a slightly different tin allocation: 0=BE, 1=LE, 2=BK, 3=VI, 4=VO more in keeping with the existing arrangement and display order 1, 2, 0, 3, 4. The shaper doesn’t appear to obviously wedge, though I have seen some latency spikes that I don’t normally see, so it feels like there’s still a corner case being hit.

Does anyone have any ideas?

Cheers,

Kevin D-B

gpg: 012C ACB2 28C6 C53E 9775  9123 B3A2 389B 9DE2 334A


             reply	other threads:[~2020-05-29 10:06 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-29 10:06 Kevin Darbyshire-Bryant [this message]
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
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=5136DAB5-B975-4D36-948D-A5A4167A8FC7@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