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>, cake@lists.bufferbloat.net
Subject: Re: [Cake] Munin-Plugins
Date: Thu, 13 Sep 2018 12:27:24 +0200	[thread overview]
Message-ID: <87pnxhheur.fsf@toke.dk> (raw)
In-Reply-To: <ae1bc187-d255-4da8-acfa-cfa32b63a2ff@email.android.com>

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?

> Also I haven't found details on the man page, but haven't looked in
> the code how exactly flows are defined for the new 2 level fair
> queueings.

A flow is a flow (hash on the regular 5-tuple). Unless you install
custom tc filters, in which case a flow could be anything you want it to
be...

> I would like to show hosts as well as flows in a graph, in the various
> states as summary as well as per tin. But hosts aren't shown in the
> statistics. But they could be helpful to see unexpected rises if
> someone is abusing the system.

Hmm, guess we could do "number of hosts per tin" accounting as well as
flows. But it would be bloating up the already bloated statistics. But
on the other hand, they are already quite bloated, so another pair of
stats maybe wouldn't make much of a difference?

Does anyone else have an opinion on this?

-Toke

  reply	other threads:[~2018-09-13 10:27 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 [this message]
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
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=87pnxhheur.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