From: Michele Petrazzo - Unipex srl <michele.petrazzo@unipex.it>
To: Jorge Bastos <mysql.jorge@decimal.pt>
Cc: 'Marek Kierdelewicz' <marek@piasta.pl>,
'Jorge Bastos' <jorge.decimal@gmail.com>,
netfilter@vger.kernel.org
Subject: Re: help on tc with kernels >= 2.6.27
Date: Sat, 03 Jan 2009 12:47:02 +0100 [thread overview]
Message-ID: <495F5036.2090104@unipex.it> (raw)
In-Reply-To: <001701c96d92$43c4e600$cb4eb200$@jorge@decimal.pt>
Jorge Bastos wrote:
> Hi Michele,
>
Ciao,
> For htb, the script Marek wrote here, shape's the traffic, but it
> gets a bit unstable, sometimes if goes down, other goes up, for a
> considered number of seconds, so I believe it's a pike.
>
I have a "big" environ with htb (kernel .26) and it works well, without
problems. Never seen up and down course.
> Here's what Marek wrote here:
<-cut->
>
> With cbq, the traffic was always stable at a constant speed, the
> oscillation wasn't more than about 1kb.
>
Also here the same.
> What I use for cbq, is the cbq.init script that generates this rules:
>
>
>
>
<-cut->
> For cbq, instead of the 20kb/sec, it goes to 1/2, sometimes 4 or 5,
> but never more than that.
>
With that rules, also here :( . Starting to say that I'm not a big tc
expert but after some test, it's seem that tbf create the problems:
if you try to remove that rule, it'll work. Also tried sfq or cbq like last
queuing and seem to shape correctly. (my test was done with scp and iptraf)
Have you tried it?
Michele
next prev parent reply other threads:[~2009-01-03 11:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-02 18:46 help on tc with kernels >= 2.6.27 Jorge Bastos
2009-01-02 19:49 ` Marek Kierdelewicz
2009-01-02 20:44 ` bsilva
[not found] ` <00c301c96d17$750ea820$5f2bf860$@jorge@decimal.pt>
2009-01-02 20:53 ` Marek Kierdelewicz
2009-01-02 20:57 ` LARTC (was: Re: help on tc with kernels >= 2.6.27) /dev/rob0
2009-01-03 10:11 ` help on tc with kernels >= 2.6.27 Michele Petrazzo - Unipex srl
[not found] ` <001701c96d92$43c4e600$cb4eb200$@jorge@decimal.pt>
2009-01-03 11:47 ` Michele Petrazzo - Unipex srl [this message]
[not found] ` <002701c96d9b$53a5c0e0$faf142a0$@jorge@decimal.pt>
2009-01-03 12:29 ` Michele Petrazzo - Unipex srl
[not found] ` <003101c96ddb$9d991310$d8cb3930$@jorge@decimal.pt>
2009-01-05 11:39 ` Michele Petrazzo - Unipex srl
[not found] ` <01ee01c96f3b$eee74fa0$ccb5eee0$@jorge@decimal.pt>
2009-01-05 14:21 ` Michele Petrazzo - Unipex srl
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=495F5036.2090104@unipex.it \
--to=michele.petrazzo@unipex.it \
--cc=jorge.decimal@gmail.com \
--cc=marek@piasta.pl \
--cc=mysql.jorge@decimal.pt \
--cc=netfilter@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