From: Anil Kumar <anilkg@gmail.com>
To: lartc@vger.kernel.org
Subject: [LARTC] ESFQ patch problem
Date: Wed, 07 Jul 2004 15:04:55 +0000 [thread overview]
Message-ID: <3045e25d0407070752538ac34d@mail.gmail.com> (raw)
I applied esfq patch to kernel then I have applied
iproute2-2.2.4-now-ss001007-esfq.diff to
patch iproute2 (tc utility, iproute2-ss010824)
source: http://www.ssi.bg/~alex/esfq/
But whenever I try to add esfq qdisc with parameter it says it donot
know the qdisc i.e esfq.
tc qdisc add dev eth0 parent 1:13 handle 13: esfq perturb 34 quantum
1514 depth 25 divisor 23 limit 34534 hash src
Unknown qdisc "esfq", hence option "perturb" is unparsable
but if I donot specify any parameters i.e
tc qdisc add dev eth0 parent 1:13 handle 13: sfq perturb 3
qdisc esfq 13: [Unknown qdisc, optlen$]
is added.
Is their some incompatibility between kernel and tc utility ?
I am working in a customized kernel with minimum functionality
(embedded applications).Is some thing missing?
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2004-07-07 15:04 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=3045e25d0407070752538ac34d@mail.gmail.com \
--to=anilkg@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox