Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Georgios Amanakis <gamanakis@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: Dave Taht <dave.taht@gmail.com>, Cake List <cake@lists.bufferbloat.net>
Subject: Re: [Cake] cake stats in the commit message?
Date: Thu, 31 May 2018 09:02:23 -0400	[thread overview]
Message-ID: <CACvFP_hxE8TurSu_QWbu3=UaMhr3+x4_nGvMS5oQ9GC-tzWRqg@mail.gmail.com> (raw)
In-Reply-To: <87vab4asin.fsf@toke.dk>

It got mangled in the email :(
It looks fine on the machine.

On Thu, May 31, 2018 at 9:01 AM, Toke Høiland-Jørgensen <toke@toke.dk> wrote:
> Georgios Amanakis <gamanakis@gmail.com> writes:
>
>> This is what my router reports right now on my humble cable Comcast.
>> The connection is advertised as 10mbps/2mbps, though they must have
>> upgraded the downstream speed to 15mbps silently.
>
> Cool. I'll add these to the commit message if we need to submit v19 :)
>
>> ens4: LAN interface
>> ens3: WAN interface
>> It is running the latest upstream-4.18 variant, on net-next.
>>
>> ----------8<----------
>> qdisc cake 8009: dev ens4 root refcnt 2 bandwidth 18Mbit diffserv3
>> dual-dsthost ingress split-gso rtt 100.0ms n    oatm overhead 18 mpu
>> 64
>>  Sent 4391082651 bytes 3197192 pkt (dropped 158915, overlimits 5952515
>> requeues 0)
>>  backlog 0b 0p requeues 0
>>  memory used: 2337560b of 4Mb
>>  capacity estimate: 18Mbit
>>  min/max network layer size:           28 /    1500
>>  min/max overhead-adjusted size:       64 /    1518
>>  average network hdr offset:           14
>>
>>                    Bulk  Best Effort        Voice
>>   thresh       1125Kbit       18Mbit     4500Kbit
>>   target         16.1ms        5.0ms        5.0ms
>>   interval      111.1ms      100.0ms      100.0ms
>>   pk_delay      146.5ms        2.6ms        694us
>>   av_delay      104.6ms        594us         51us
>>                                          84   sp_delay        4.3ms
>>       1us         12us
>
> Did this get mangled in the email or does it look like this on your
> machine as well?
>
> -Toke

  reply	other threads:[~2018-05-31 13:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-30 21:36 Dave Taht
2018-05-31 12:58 ` Georgios Amanakis
2018-05-31 13:01   ` Toke Høiland-Jørgensen
2018-05-31 13:02     ` Georgios Amanakis [this message]
2018-05-31 13:04       ` 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='CACvFP_hxE8TurSu_QWbu3=UaMhr3+x4_nGvMS5oQ9GC-tzWRqg@mail.gmail.com' \
    --to=gamanakis@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    --cc=dave.taht@gmail.com \
    --cc=toke@toke.dk \
    /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