From: Amit Kucheria <amitk@ittc.ku.edu>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HTB3 port for 2.2.18?
Date: Sun, 25 Aug 2002 21:01:38 +0000 [thread overview]
Message-ID: <marc-lartc-103030936209175@msgid-missing> (raw)
In-Reply-To: <marc-lartc-102953133832346@msgid-missing>
On Sun, 25 Aug 2002, Julian Anastasov wrote:
> # 3 GRED qdiscs for the 3 drop priorities of real time packets
> -$TC qdisc add $DEV parent 2:1 gred limit 12KB min 3KB max 9KB \
> +$TC qdisc change $DEV parent 2:1 gred limit 12KB min 3KB max 9KB \
> burst 20 $AVPKT $BW DP 1 probability 0.02 prio 2
> -$TC qdisc add $DEV parent 2:1 gred limit 12KB min 3KB max 9KB \
> +$TC qdisc change $DEV parent 2:1 gred limit 12KB min 3KB max 9KB \
> burst 20 $AVPKT $BW DP 2 probability 0.04 prio 3
> -$TC qdisc add $DEV parent 2:1 gred limit 12KB min 3KB max 9KB \
> +$TC qdisc change $DEV parent 2:1 gred limit 12KB min 3KB max 9KB \
> burst 20 $AVPKT $BW DP 3 probability 0.06 prio 4
> i.e. first time it is "qdisc add", later the qdisc is changed
> with "qdisc change".
>
> Let me know if this is the only problem and whether
> GRED is working properly. Thanks.
Hi,
It works now! It seems to me that the semantics of the GRED qdisc with
respect to 'tc' have changed. The script I had provided worked with CBQ
i.e. 'qdisc add' was used 3 times to add the GRED qdiscs with different
drop probabilities.
Thanks a lot.
Regards,
Amit
--
I'm an angel!!! Honest!
The horns are just there to hold the halo up straight.
^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^-^
Amit Kucheria
EECS Grad. Research Assistant
University of Kansas @ Lawrence
(R): +1-785-830-8521 ||| (C): +1-785-760-2871
____________________________________________________
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2002-08-25 21:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-16 20:54 [LARTC] HTB3 port for 2.2.18? Amit Kucheria
2002-08-17 9:25 ` Julian Anastasov
2002-08-19 17:47 ` Amit Kucheria
2002-08-25 21:01 ` Amit Kucheria [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-103030936209175@msgid-missing \
--to=amitk@ittc.ku.edu \
--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.