Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: "Toke Høiland-Jørgensen" <toke@toke.dk>
To: Ruben <ruben@vfn-nrw.de>
Cc: cake@lists.bufferbloat.net
Subject: Re: [Cake] Munin-Plugins
Date: Wed, 19 Sep 2018 11:11:36 +0200	[thread overview]
Message-ID: <87va71kg1j.fsf@toke.dk> (raw)
In-Reply-To: <1645d6fe-d5f2-4416-beed-ae5ac71170f8@email.android.com>

Ruben <ruben@vfn-nrw.de> writes:

> Hey Toke,
>
> Am 13.09.2018 21:12 schrieb Toke Høiland-Jørgensen <toke@toke.dk>:
>
>
>     Ruben <ruben@vfn-nrw.de> writes:
>
>     > Hey Toke,
>     >
>     > Thanks for your fast response!
>     >
>     > Am 13.09.2018 12:27 schrieb Toke Høiland-Jørgensen <toke@toke.dk>:
>     >
>     >
>     >     Ruben <ruben@vfn-nrw.de> writes:
>     >
>     >     > Hey guys,
>     >     >
>     >     > I've already mentioned this in a response to dtaht on GitHub, but
>     here
>     >     > again for everyone:
>     >     >
>     >     > I was wondering if it's possible to extend the tin statistics by
>     >     > packets for backlog.
>     >
>     >     Why do you need packets when there's already bytes?
>     >
>     > Easy: dtaht requested a packets graph with ecn marks, which is also
>     > packets, so backlog as bytes do not fit, backlog as packets do.
>     >
>     > The idea was to do a multi-graph which is one graph with combined
>     > stats for all tins and sub graphs for all tins.
>     >
>     > On the main graph a backlog in packets is available, but I would need
>     > to leave out the backlog for the tins, which is somewhat confusing.
>
>     Why not just do both backlogs in bytes?
>
> There's no counter for ecn marked packets in bytes, so it's impossible to
> implement it that way, too.
>
> ECN-Marks is in packets, so everything else need to be in packets as
> well.

Hmm, so the obvious follow-up question would be "why do you need to have
backlog and number of drops on the same graph?" :)

-Toke

  reply	other threads:[~2018-09-19  9:11 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-09-11  2:22 Ruben
2018-09-11 10:44 ` Georgios Amanakis
2018-09-13  9:35 ` Ruben
2018-09-13 10:27   ` Toke Høiland-Jørgensen
2018-09-13 19:00     ` Ruben
2018-09-13 19:12       ` Toke Høiland-Jørgensen
2018-09-19  3:35         ` Ruben
2018-09-19  9:11           ` Toke Høiland-Jørgensen [this message]
2018-09-19 17:01             ` Dave Taht
2018-09-20  1:35               ` Ruben
2018-09-20  1:39             ` Ruben
2018-09-20  2:13               ` Jonathan Morton

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=87va71kg1j.fsf@toke.dk \
    --to=toke@toke.dk \
    --cc=cake@lists.bufferbloat.net \
    --cc=ruben@vfn-nrw.de \
    /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