From: devik <devik@cdi.cz>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] tc class show problem with HTB ?
Date: Thu, 03 Jan 2002 11:48:58 +0000 [thread overview]
Message-ID: <marc-lartc-101005915503306@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101004242007129@msgid-missing>
Hello. Rolf Fokkens already send me patch to this. In 2.4.17 there is
change in kernel which causes this bug. As quick repair add line:
#define CONFIG_RTNETLINK 1
just before line:
#define HTB_HSIZE 16
it should help. I'll produce new patch for 2.4.17 but time
is my enemy just now.
devik
On Thu, 3 Jan 2002, Tommy Wu wrote:
> Hi!
>
> I'm using 2.4.17 + htb2_2.4.16.diff now.
> But I found the tc class show command won't show the correct infomation like before...
> I got something like:
>
> # tc -s -d class show dev eth0
> class htb 1: parent 1:
> class htb 1: parent 1:
> class htb 1: parent 1:
> class htb 1: parent 1:
> class htb 1: parent 1:
> class htb 1: parent 1:
> class htb 1: parent 1:
>
> # tc -s qdisc
> qdisc ingress ffff: dev eth0
> Sent 0 bytes 0 pkts (dropped 0, overlimits 0)
>
> qdisc sfq 99: dev eth0 quantum 1514b perturb 10sec
> Sent 209435 bytes 1201 pkts (dropped 0, overlimits 0)
>
> qdisc sfq 32: dev eth0 quantum 1514b perturb 10sec
> Sent 8533 bytes 79 pkts (dropped 0, overlimits 0)
>
> qdisc sfq 31: dev eth0 quantum 1514b perturb 10sec
> Sent 664840 bytes 874 pkts (dropped 0, overlimits 0)
>
> qdisc sfq 20: dev eth0 quantum 1514b perturb 10sec
> Sent 16200 bytes 288 pkts (dropped 0, overlimits 0)
>
> qdisc sfq 10: dev eth0 quantum 1514b perturb 10sec
> Sent 32727 bytes 327 pkts (dropped 0, overlimits 0)
>
> qdisc htb 1: dev eth0
> Sent 931735 bytes 2769 pkts (dropped 0, overlimits 912)
>
> Is there any patch I miss ?
> The old HTB patch for 2.4.14 show correct infomation here, but it'll got
> message like HTB timer > 5 sec...
>
> --
>
> Tommy Wu
> mailto:tommy@teatime.com.tw
> http://www.teatime.com.tw/~tommy
> ICQ: 22766091
> Mobile Phone: +886 936 909490
> TeaTime BBS +886 2 31515964 24Hrs V.Everything
>
>
>
>
> _______________________________________________
> LARTC mailing list / LARTC@mailman.ds9a.nl
> http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/lartc/
prev parent reply other threads:[~2002-01-03 11:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-01-03 7:19 [LARTC] tc class show problem with HTB ? Tommy Wu
2002-01-03 11:48 ` devik [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-101005915503306@msgid-missing \
--to=devik@cdi.cz \
--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.