Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Jonathan Morton <chromatix99@gmail.com>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] CS1 behavior in diffserv4
Date: Fri, 19 Jun 2015 19:50:48 -0700	[thread overview]
Message-ID: <CAA93jw6Ka51ocgfffAruwQ0s+98FbJkZA2ahVOQgRAH-z3iXWQ@mail.gmail.com> (raw)
In-Reply-To: <97E8CD56-7AC5-4D0D-8B29-0E8C48FF8C5C@gmail.com>

yes, that clobbered the transmission stuff. I wlll argue that "class"
is a lousy name, and misleading to see the rate so....

With the correctly marked CS1 stuff, now, torrent backed way off.

root@ranger:~# watch tc -s qdisc show dev eth2
root@ranger:~# tc -s qdisc show dev eth2
qdisc cake 8014: root refcnt 9 bandwidth 10Mbit diffserv4 flows raw
 Sent 165054263 bytes 534623 pkt (dropped 7727, overlimits 1035673 requeues 0)
 backlog 49462b 26p requeues 0
           Class 0     Class 1     Class 2     Class 3
  rate        10Mbit    9375Kbit    7500Kbit    2500Kbit
  target       5.0ms       5.0ms       5.0ms       7.3ms
interval     100.0ms     100.0ms     100.0ms     102.3ms
Pk delay     215.9ms      28.0ms       445us        11us
Av delay      39.9ms       3.8ms         8us         0us
Sp delay       2.9ms       578us         8us         0us
  pkts         43184      499206           3           1
way inds         323         137           0           0
way miss        1788        1338           3           1
way cols           0           0           0           0
  bytes     51178018   122599036         270          46
  drops         6398        1329           0           0
  marks            0           0           0           0
qdisc ingress ffff: parent ffff:fff1 ----------------
 Sent 1229901568 bytes 919416 pkt (dropped 0, overlimits 0 requeues 0)
 backlog 0b 0p requeues 0

On Fri, Jun 19, 2015 at 7:40 PM, Jonathan Morton <chromatix99@gmail.com> wrote:
>
>> On 20 Jun, 2015, at 05:19, Dave Taht <dave.taht@gmail.com> wrote:
>>
>> I have to admit I thought diffserv4 put CS1 in class 3?
>
> No - class 0 is background, 1 is best-effort, 2 is “video” and 3 is “voice”.  So it’s working just fine.
>
> Try making some best-effort traffic compete with it, and see how the relative throughputs go.
>
>  - Jonathan Morton



-- 
Dave Täht
worldwide bufferbloat report:
http://www.dslreports.com/speedtest/results/bufferbloat
And:
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast

  reply	other threads:[~2015-06-20  2:50 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-20  2:19 Dave Taht
2015-06-20  2:40 ` Jonathan Morton
2015-06-20  2:50   ` Dave Taht [this message]
2015-06-20  2:57     ` 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=CAA93jw6Ka51ocgfffAruwQ0s+98FbJkZA2ahVOQgRAH-z3iXWQ@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=chromatix99@gmail.com \
    /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