Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Kevin Darbyshire-Bryant <kevin@darbyshire-bryant.me.uk>
To: <cake@lists.bufferbloat.net>
Subject: Re: [Cake] cake stats 1+ stuff not big on
Date: Mon, 5 Oct 2015 10:22:38 +0100	[thread overview]
Message-ID: <5612415E.5000209@darbyshire-bryant.me.uk> (raw)
In-Reply-To: <56123BD1.2040902@darbyshire-bryant.me.uk>

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



On 05/10/15 09:58, Kevin Darbyshire-Bryant wrote:
>
> On 04/10/15 23:40, Dave Taht wrote:
>> what does 1+ mean?
>>
>> I do not like this because it really messes with simple parsers of the
>> resulting data. Key/vaue pairs only please. I have similar feelings
>> about "way inds", and would prefer that sort of stuff way-inds.
>>
>>
>>
> Would https://github.com/dtaht/tc-adv/pull/6 be acceptable to your
> sight? :-)
>
> Actually I've just spotted another little tweak to do....there'll be
> another commit in a little while.....like busses these commits ;-)
And merged with my freshly bestowed super-cow^H^H^Hmerge powers

I didn't think I suffered from OCD but I have to say that 'max-len' not
lining up is bringing it out..hmmmm!

root@Router:~# tc -s qdisc show dev ifb4eth0
qdisc cake 800b: root refcnt 2 bandwidth 39300Kbit diffserv4 flows noatm
overhead 12
 Sent 161649 bytes 721 pkt (dropped 0, overlimits 47 requeues 0)
 backlog 0b 0p requeues 0
             Bin 0       Bin 1       Bin 2       Bin 3 
  rate     39300Kbit   36843Kbit   29475Kbit    9825Kbit
  target       5.0ms       5.0ms       5.0ms       5.0ms
interval     100.0ms     100.0ms     100.0ms     100.0ms
Pk-delay         0us        82us         0us         0us
Av-delay         0us         7us         0us         0us
Sp-delay         0us         1us         0us         0us
  pkts             0         721           0           0
way-inds           0           0           0           0
way-miss           0         104           0           0
way-cols           0           0           0           0
  bytes            0      161649           0           0
  drops            0           0           0           0
  marks            0           0           0           0
Sp-flows           0           0           0           0
Blkflows           0           2           0           0
last-len           0          82           0           0
max-len            0        1514           0           0









[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/pkcs7-signature, Size: 4816 bytes --]

  reply	other threads:[~2015-10-05  9:22 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-04 22:40 Dave Taht
2015-10-05  8:58 ` Kevin Darbyshire-Bryant
2015-10-05  9:22   ` Kevin Darbyshire-Bryant [this message]
2015-10-05  9:34     ` Dave Taht
2015-10-05  9:46       ` Kevin Darbyshire-Bryant
2015-10-05  9:55         ` Toke Høiland-Jørgensen
2015-10-05 10:05           ` Sebastian Moeller
2015-10-05  9:40 ` Toke Høiland-Jørgensen

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=5612415E.5000209@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