From: Kennedy Cheng <kennedy.cheng@jungle.bt.co.uk>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] how to add my own traffic scheduler to TC
Date: Thu, 04 Mar 2004 11:47:02 +0000 [thread overview]
Message-ID: <40471736.253D0796@jungle.bt.co.uk> (raw)
In-Reply-To: <4045F71E.EE590F91@jungle.bt.co.uk>
Thanks Roy, I found the answers. I didn't know I had to modify the kernel QoS
library (which I did) as well as the iproute2 library (which I didn't). It is
working now :)
Thanks,
Kennedy
Roy wrote:
> TC is like iptables, you need to add suport to tc binary for your module,
> else you wont be able to configure it.
> I dont know how to do this , but try to find some analogy with other modules
> you will need to modify tc makefile, and add aditional module.
>
> ----- Original Message -----
> From: "Kennedy Cheng" <kennedy.cheng@jungle.bt.co.uk>
> To: <lartc@mailman.ds9a.nl>
> Sent: Wednesday, March 03, 2004 5:17 PM
> Subject: [LARTC] how to add my own traffic scheduler to TC
>
> > What are the steps needed to add my own traffic scheduler to
> > TC?
> >
> > My understanding is that I need to do something in the net/sched/
> > directory: add a schedular eg sch_blue.c, change the Makefile, config.in
> > and sch_api.c; add the appropriate qopt, xstats struct... in the
> > include/linux/pkt_sched.h. I've got it all compiled without warnings or
> > error. When I typed '"'tc add dev eth0 root blue limit 1000kB......'"', it
> > complained '"'Unknown qdisc '"'blue'"', hence option '"'limit'"' is
> > unparsable'"'.
> > When I typed '"'tc add dev eth0 root red limit 1000kB.....'"', it worked
> > fine (of course).
> >
> > The code I wrote was a complete copy of the sch_red.c, with text changed
> > to blue instead of red. TC is not happy with my blue scheduler. What
> > have I done wrong? Have I missed something?
> >
> > Linux Kernel version 2.4.20-8
> >
> > Many Thanks,
> > Kennedy
> >
> >
> > _______________________________________________
> > LARTC mailing list / LARTC@mailman.ds9a.nl
> > http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
> >
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2004-03-04 11:47 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-03 15:17 [LARTC] how to add my own traffic scheduler to TC Kennedy Cheng
2004-03-03 16:46 ` Roy
2004-03-04 11:47 ` Kennedy Cheng [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=40471736.253D0796@jungle.bt.co.uk \
--to=kennedy.cheng@jungle.bt.co.uk \
--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;
as well as URLs for NNTP newsgroup(s).