From: Andreas Klauer <Andreas.Klauer@metamorpher.de>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB: far unequal behaivor at a slight conf rate change
Date: Thu, 23 Feb 2006 22:38:35 +0000 [thread overview]
Message-ID: <20060223223835.GA23114@EIS> (raw)
In-Reply-To: <200602231908.27900.luciano@lugmen.org.ar>
On Thu, Feb 23, 2006 at 07:08:27PM -0300, Luciano Ruete wrote:
> root->parent_all_host(256,256)->client_host_1(X,X)->host_1_prio(X*0.9,X)
> ->host_1_dfl(X*0.1,X)
What's the purpose of the 256kbit class? In the setup you posted,
the 200/230kbit child class does not seem to have any siblings.
Except for the root class, classes without siblings don't make sense.
At least, I haven't seen any useful purpose for them so far.
> I've attached simplified ad-hoc scripts that reproduce the scenarios:
> tc_at_200 (full tc/iptables commands to recreate the X<200 scenario)
> tc_at_230 (full tc/iptables commands to recreate the X>200 scenario)
I haven't tested them, but they seem to be all right (except for the
question above). I don't know if it will help at all, but could you
post tc statistics for both 200 and 230 cases? You can get the statistics
using 'tc -s -d qdisc/class show dev $iface' or similar command.
Also, did you check wether HTB is complaining about anything in dmesg
when setting up the 230 class tree?
Which kernel version and iproute/tc version are you running? Just in case
you're still suffering from old HTB bugs...
Regards
Andreas Klauer
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
next prev parent reply other threads:[~2006-02-23 22:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-23 22:08 [LARTC] HTB: far unequal behaivor at a slight conf rate change Luciano Ruete
2006-02-23 22:38 ` Andreas Klauer [this message]
2006-02-24 2:42 ` Luciano Ruete
2006-02-24 9:36 ` Andreas Klauer
-- strict thread matches above, loose matches on Subject: below --
2006-02-25 11:06 Luciano Ruete
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=20060223223835.GA23114@EIS \
--to=andreas.klauer@metamorpher.de \
--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