Grace Baldonasa wrote: > > I have a few question: > 1. Is there any packages for CBQ or HTB that I can just compiled > for ARM again. No. Kernel modules must be built using the .config file in /usr/src/linux and are specific to the things that are specified therein. It is not possible to compile a standalone module for any scheduler (or much of anything else, for that matter). (It is possible to change the source to a previously compiled module and RE compile that.) > I dont want to compile the kernel again, so if I could get the > CBQ & HTB packages, it'll make my life easier. Sorry, your life cannot be made easier. > 2. Aside from having these modules, what else should i add? (e.g.: > config files, init scripts.. etc) Jim DiGriz' (a nom de plume for Alexander Clouter - whose name I've just misspelled) stuff is "the place" to start: http://digriz.org.uk/ > 3. If at any case I uses both HTB & CBQ would it be okay if both of > these modules are loaded? Yes, certainly. You'll also have modules for u32 and (e)sfq and perhaps others like ingress policing loaded all at the same time. > Thanks for the time. > > Grace > > > On 4/27/05, gypsy <gypsy@xxxxxxxxxx> wrote: > > Grace Baldonasa wrote: > > > > Hi All, > > > > I cross compiled and run tc in arm platform. > > When I tried executing it I got this error. > > > > tc qdisc add dev eth0 root handle 1:0 cbq bandwidth > 100Mbit avpkt 1000 > > mpu 64 > > RTNETLINK answers: Invalid argument > > > > Is there something I'm missing here... > > > > Thanks. > > > > Grace > > I don't know what "arm" is. > > Are you certain that the CBQ module loaded? Yes, it should > be a module, > not built into the kernel. > > First make sure that there is only one TC executable on your > system. > Then try a few different TC commands: > > tc -s qdisc ls dev eth0 > tc -s class ls dev eth0 > tc qdisc add dev eth0 root handle 1: htb default 30 > > If the htb works then the problem is, of course, cbq. If > both cbq and > htb fail but the "show" commands above work, then I can't > help. But if > all fail, your cross compile was bad. > > Also try > modprobe sch_cbq > modprobe -r sch_cbq > modprobe sch_htb > modprobe -r sch_htb > and watch your logs. > > gypsy _______________________________________________ LARTC mailing list LARTC@xxxxxxxxxxxxxxx http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
