All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andy Furniss <andy.furniss@dsl.pipex.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB weird problem ....
Date: Fri, 08 Oct 2004 14:58:46 +0000	[thread overview]
Message-ID: <4166AB26.8040201@dsl.pipex.com> (raw)
In-Reply-To: <20041008014007.4421.qmail@web50305.mail.yahoo.com>

Drink Linux wrote:
> hello Andy , i think they are right for 
> 256kbps = 2048kbit ...

ahh I see.

I just tried your setup on my eth0 and it works OK. Though HTB's stats 
don't seem too accurate - I used wget/ftp to judge rates.

You may need to patch HTB/use a newer kernel - there was a patch posted 
on this list a while back which may affect you.

Also you may need to set Hz higher or use psched = CPU for timing.

See www.docum.org .

> 
> 
> i have added a leaf pfifo with a limit of 1 packet per
> second, coz if i have 2-10 it wont work...viola !!!
> the ceiling rate for each class rule is now working...
> my problem is that you can reach the ceiling class
> only if you have 4-5 files getting through FTP, 
> 
> ex: 256kbps Ceil
> 
>     1 file ftp download = 80-90 kbps max speed 
>     4-5 files ftp download = almost 256kbps
> 
> 
> how can i make it work to 256kbps speed for 1 file
> alone ...? 

Get rid of the 1 packet pfifo :-)

Andy.




_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

  parent reply	other threads:[~2004-10-08 14:58 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-08  1:40 [LARTC] HTB weird problem Drink Linux
2004-10-08 12:36 ` Andy Furniss
2004-10-08 13:04 ` Drink Linux
2004-10-08 14:58 ` Andy Furniss [this message]
2004-10-08 15:06 ` Jason Boxman
2004-10-09  8:50 ` Drink Linux
2004-10-09 13:04 ` Andy Furniss

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=4166AB26.8040201@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.