From: Thomas Jalsovsky <admin@postel.sk>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB problems
Date: Mon, 09 Dec 2002 15:50:45 +0000 [thread overview]
Message-ID: <marc-lartc-103944911317470@msgid-missing> (raw)
In-Reply-To: <marc-lartc-103944562212642@msgid-missing>
On Mon, 9 Dec 2002, Thomas Jalsovsky wrote:
> On Mon, 9 Dec 2002, Vladimir Smelhaus wrote:
>
> > On 9 Dec 2002, 15:52, Thomas Jalsovsky wrote:
> >
> > > I have HTB on IMQ device. My rate does not work as I configured. I
> > > configured 1920kbit/s and I can download only about 290kbit/s (while
> >
> > Set your pfifo limit higher. You have too much dropped packets.
> >
> > > class htb 1:10 parent 1:1 leaf 10: prio 0 quantum 9011 rate 704Kbit
> > > ceil 1920Kbit burst 2500b/8 mpu 0b cburst 4056b/8 mpu 0b level 0
> > > Sent 8642235 bytes 8393 pkts (dropped 2153, overlimits 0)
> > > rate 36918bps 36pps
> > > lended: 3618 borrowed: 4775 giants: 0
> I have:
> ifconfig imq0
> imq0 Link encap:UNSPEC HWaddr
> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
> UP RUNNING NOARP MTU:1500 Metric:1
> RX packets:821349 errors:0 dropped:0 overruns:0 frame:0
> TX packets:723509 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:30
> RX bytes:456249915 (435.1 Mb) TX bytes:391405155 (373.2 Mb)
>
> Which value if txqueuelen should be good for me? Or you though for
> anything else (in lartc pfifo limit is txqueuelen..)
Sorry, it was my mistake, I had limit 2 in my configuration. Now I have
the default - 30p - and it works fine for me.
Thank you for your help.
Regards,
Thomas
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-12-09 15:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-09 14:52 [LARTC] HTB problems Thomas Jalsovsky
2002-12-09 15:11 ` Vladimir Smelhaus
2002-12-09 15:35 ` Thomas Jalsovsky
2002-12-09 15:50 ` Thomas Jalsovsky [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=marc-lartc-103944911317470@msgid-missing \
--to=admin@postel.sk \
--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.