Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Y <intruder_tkyf@yahoo.fr>
To: cake@lists.bufferbloat.net
Subject: Re: [Cake] Diffserv LLT mode
Date: Sat, 21 Apr 2018 21:40:48 +0900	[thread overview]
Message-ID: <20180421214016.0c18ae9f@raspberrypi> (raw)
In-Reply-To: <CE4467AF-B06F-421C-9C37-A4A6D1AA4069@eventide.io>

Hi.

mine stat doen't  inclued more.
sad.

yutaka

pi@raspberrypi:~ $ tc -s -d qdisc
qdisc noqueue 0: dev lo root refcnt 2 
 Sent 0 bytes 0 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
qdisc cake 8017: dev eth0 root refcnt 2 bandwidth 810Kbit diffserv3
srchost rtt 100.0ms raw atm overhead -4 Sent 42114643 bytes 197572 pkt
(dropped 232, overlimits 73726 requeues 0) backlog 0b 0p requeues 0

qdisc ingress ffff: dev eth0 parent ffff:fff1 ---------------- 
 Sent 192984793 bytes 176545 pkt (dropped 0, overlimits 0 requeues 0) 
 backlog 0b 0p requeues 0
qdisc cake 8016: dev ifb0 root refcnt 2 bandwidth 11500Kbit diffserv3
dsthost rtt 100.0ms raw atm overhead -4 Sent 195434409 bytes 176530 pkt
(dropped 14, overlimits 107096 requeues 0) backlog 0b 0p requeues 0


On Sat, 21 Apr 2018 10:44:19 +0200
Pete Heist <pete@eventide.io> wrote:

> > On Apr 19, 2018, at 4:50 PM, Toke Høiland-Jørgensen <toke@toke.dk>
> > wrote:
> > 
> > Is anyone actually using the LLT diffserv setting?  
> 
> I re-tested diffserv-llt quickly using the current head of cake and
> tc-adv and am confused by something:
> 
> http://drhleny.cz/bufferbloat/cake/round5/diffserv_rrul_eg_cake_ds-llt_50mbit/index.html
> 
> When I look at the qdisc stats for cake, there are 5 tins: Low Loss,
> Best Effort, Low Delay, Bulk and Net Control. Shouldn’t the Low Delay
> tin have its target and interval reduced to something below 5ms and
> 100ms? And the bulk tin has a target and interval of 5.8ms and
> 100.8ms(?)
> 
> In short, I forget how diffserv-llt was supposed to work, regardless
> of whether or not it’s on the chopping block. No need for a history
> lesson if it will be removed… :)
> 
> Improved intra-flow latency could be useful for HTTP/2 or other
> things, but I don’t see how the current llt mode helps most ordinary
> people with that, when it would only apply to flows with certain
> diffserv markings, and doesn’t seem to adjust the target and interval
> anyway… _______________________________________________ Cake mailing
> list Cake@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cake




  reply	other threads:[~2018-04-21 12:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-19 14:50 Toke Høiland-Jørgensen
2018-04-20 19:39 ` Toke Høiland-Jørgensen
2018-04-20 20:04   ` Dave Taht
2018-04-21  8:44 ` Pete Heist
2018-04-21 12:40   ` Y [this message]
2018-04-21 16:44   ` Jonathan Morton
2018-04-22  6:15     ` Pete Heist
2018-04-22 10:45       ` Toke Høiland-Jørgensen
     [not found]   ` <mailman.249.1524314463.3573.cake@lists.bufferbloat.net>
2018-04-22 10:46     ` Toke Høiland-Jørgensen
2018-04-23  1:43       ` Y
     [not found]       ` <mailman.252.1524447808.3573.cake@lists.bufferbloat.net>
2018-04-23  4:39         ` Jonathan Morton
2018-04-23  5:46           ` Y

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=20180421214016.0c18ae9f@raspberrypi \
    --to=intruder_tkyf@yahoo.fr \
    --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