From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Strange HFSC behavior - bug? my misconfiguration/lack
Date: Mon, 16 May 2005 18:50:32 +0000 [thread overview]
Message-ID: <4288EB78.3080309@dsl.pipex.com> (raw)
In-Reply-To: <200505142320.13732.marcin_ml@sekretarka.no-ip.org>
Marcin Ka³u¿a wrote:
> Hi
> I'm moving to hfcs (mostly succesfuly:) ), but I've encountered a strange
> problem: When I download something from this server using wget (one thread)
> via an idle uplink, I get no more than 130 kbit/s, and when I'm using
> prozilla (or start more wgets), I get about 200 kbit, but still it's not all
> the link can do (240) - the rest remamins unused.
> Is this my fault or the qdisc? (I must tell that htb works fine - I get all
> the bandwidth I can no matter how many threads I use)
>
> I enclose my config below
>
> ---------------------------cut---------------------------
> $uplink$0kbit
This should be uplink$0kbit.
As you use imq and haven't shown the other rules I can't tell if
everythings going to the right places - can you see everythings going to
the right place with
tc -s class ls dev imq0.
Depending on kernel version some people have had problems with imq.
The hfsc parts of the script ratelimited accuratly for me.
Andy.
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
prev parent reply other threads:[~2005-05-16 18:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-14 21:20 [LARTC] Strange HFSC behavior - bug? my misconfiguration/lack of Marcin Kałuża
2005-05-16 18:50 ` 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=4288EB78.3080309@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