From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HFSC and default qdisc backlog
Date: Wed, 12 Apr 2006 15:04:33 +0000 [thread overview]
Message-ID: <443D1701.4070404@dsl.pipex.com> (raw)
In-Reply-To: <033e01c64d41$fd1ae8d0$1414a8c0@provsol.int>
James Nelson wrote:
> Thanks for all of your help Patrick!
>
> Just so I'm clear. If hfsc at the class level shows no overlimits and no
> packet dropps, then hfsc is not effecting my traffic any different (from a
> throughput perspective computational computer slowness aside) then if i had
> no traffic shapping in place?
Noting what Patrick says as a caveat. But if you set up a rt class in
hfsc at the moment (it may change soon) you can sort of get a feel for
what's gone on historically by looking at the requeue counters (can't
remember if tc -s class ls will do or tc -s qdisc ls with child queues
on the class is needed).
If you have a rt class you probably don't want it to ever be backlogged
- it won't be very rt anymore (OK you could have short queue & drop).
If a rt class has become backlogged in the past then you will see
requeues - it may not be perfect, but I would say big number = bad, 0 =
good.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2006-04-12 15:04 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 23:48 [LARTC] HFSC and default qdisc backlog James Nelson
2006-03-22 0:03 ` Patrick McHardy
2006-03-23 0:13 ` James Nelson
2006-03-23 0:27 ` Jason Boxman
2006-03-23 4:03 ` Patrick McHardy
2006-04-12 15:04 ` Andy Furniss [this message]
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=443D1701.4070404@dsl.pipex.com \
--to=andy.furniss@dsl.pipex.com \
--cc=lartc@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