Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Grace Baldonasa <gbaldona@gmail.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] invalid argument
Date: Fri, 29 Apr 2005 04:13:01 +0000	[thread overview]
Message-ID: <7034e7b5050428211346dbcce7@mail.gmail.com> (raw)
In-Reply-To: <marc-lartc-103659718601296@msgid-missing>


[-- Attachment #1.1: Type: text/plain, Size: 1865 bytes --]

Hi,
Thanks for the info.
I cross compiled tc targeted to XSCALE platform. When i was trying to 
execute the tc commands that's when I encountered this invalid argument 
problem.
So now I understand, CBQ, HTB are kernel modules that needs to be loaded as 
well to use tc. 

I have a few question:
1. Is there any packages for CBQ or HTB that I can just compiled for ARM 
again.
I dont want to compile the kernel again, so if I could get the CBQ & HTB 
packages, it'll make my life easier.
2. Aside from having these modules, what else should i add? (e.g.: config 
files, init scripts.. etc)
3. If at any case I uses both HTB & CBQ would it be okay if both of these 
modules are loaded?

Thanks for the time.

Grace




On 4/27/05, gypsy <gypsy@iswest.com> 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
>

[-- Attachment #1.2: Type: text/html, Size: 2438 bytes --]

[-- Attachment #2: Type: text/plain, Size: 143 bytes --]

_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc

  parent reply	other threads:[~2005-04-29  4:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-11-06 15:37 [LARTC] Invalid Argument Emmanuel Khamissian
2002-11-06 16:57 ` Stef Coene
2002-11-06 17:04 ` David Boreham
2005-04-27  7:00 ` [LARTC] invalid argument Grace Baldonasa
2005-04-27 14:12 ` gypsy
2005-04-29  4:13 ` Grace Baldonasa [this message]
2005-04-29 14:08 ` gypsy

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=7034e7b5050428211346dbcce7@mail.gmail.com \
    --to=gbaldona@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