From: Patrick McHardy <kaber@trash.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] HFSC
Date: Sat, 28 Feb 2004 06:22:12 +0000 [thread overview]
Message-ID: <40403394.3020508@trash.net> (raw)
In-Reply-To: <marc-lartc-98548596122489@msgid-missing>
syrius.ml@no-log.org wrote:
> syrius.ml@no-log.org writes:
>
>
>>where can i find more informations and examples about the *linux* HFSC
>>?
>>http://trash.net/~kaber/hfsc/ does not help here
>
>
> the patch http://trash.net/~kaber/hfsc/ provides compiles correctly
> when applied on
> ftp://ftp.inr.ac.ru/ip-routing/iproute2-2.4.7-now-ss020116-try.tar.gz
> but not on ss010824.
>
> # tc qdisc add dev eth0 root hfsc help
> Usage: ... hfsc [ default CLASSID ]
>
> # tc qdisc add dev eth0 root hfsc default 1:10
> HFSC: Illegal "default"
Default is just a class ID in the namespace of the qdisc,
so you can't specify a handle:
tc qdisc add dev eth0 root hfsc default 10
Regards
Patrick
>
> (same results without the "root" option)
>
>
> without talking about the wireless features, what's the difference
> between http://trash.net/~kaber/hfsc and http://wsched.sf.net hfsc ?
>
> what are rt, ls and ul service curves ?
>
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2004-02-28 6:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-03-25 2:14 [LARTC] HFSC Rick Goh
2004-02-26 2:39 ` syrius.ml
2004-02-26 13:39 ` Patrick McHardy
2004-02-28 2:59 ` syrius.ml
2004-02-28 6:22 ` Patrick McHardy [this message]
2004-02-28 6:42 ` Patrick McHardy
2004-05-12 16:36 ` Lawrence MacIntyre
2004-05-13 13:05 ` Patrick McHardy
2004-05-13 13:52 ` Lawrence MacIntyre
2004-05-13 14:23 ` Patrick McHardy
2004-05-13 17:43 ` Lawrence MacIntyre
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=40403394.3020508@trash.net \
--to=kaber@trash.net \
--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.