From: Patrick McHardy <kaber@trash.net>
To: Denys <denys@visp.net.lb>
Cc: netdev@vger.kernel.org
Subject: Re: HFSC dangerous behaviour (not a bug)
Date: Mon, 29 Oct 2007 11:56:52 +0100 [thread overview]
Message-ID: <4725BC74.9040407@trash.net> (raw)
In-Reply-To: <20071029005547.M47431@visp.net.lb>
Denys wrote:
> Additionally, it doesn't show rate in stats (so it is difficult to measure,
> how much is really using each class).
>
> qdisc hfsc 1: root default 200
> Sent 1392761062 bytes 965768 pkt (dropped 52, overlimits 1620539 requeues 0)
> rate 0bit 0pps backlog 0b 0p requeues 0
Thats what rate estimators are for. Add something like "estimator 1 4"
to your qdisc and class creation commands to measure the rate.
next prev parent reply other threads:[~2007-10-29 10:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-29 0:55 HFSC dangerous behaviour (not a bug) Denys
2007-10-29 10:56 ` Patrick McHardy [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-10-29 0:02 Denys
2007-10-29 10:55 ` Patrick McHardy
2007-10-29 11:45 ` Denys
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4725BC74.9040407@trash.net \
--to=kaber@trash.net \
--cc=denys@visp.net.lb \
--cc=netdev@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).