From: Stef Coene <stef.coene@docum.org>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Explanation reqd. for few (more than few!) concepts in TC <long>
Date: Fri, 31 Oct 2003 09:47:07 +0000 [thread overview]
Message-ID: <marc-lartc-106759372412293@msgid-missing> (raw)
In-Reply-To: <marc-lartc-106732522922215@msgid-missing>
On Friday 31 October 2003 08:23, Suraj Shankar wrote:
> > Don't trust the help function :(. My tip : go to
> > http://docum.org, go to the
> > test pages and copy my cbq commands ,)
>
> okey! now I understand what you earlier meant by test
> pages. Was there, you syntax works ... which means the
> tc help isn't exhaustive, well that's a pity. Thank
> you. Do you have any pointers to where I can find a
> list of parameters configurable with a particular
> queue?
Not really. The htb parameters are easy to understand. The cbq parameters
are not. Some information can be found in the tc source, some in the kernel
source. That's one of the reasons I suggest htb.
Stef
--
stef.coene@docum.org
"Using Linux as bandwidth manager"
http://www.docum.org/
#lartc @ irc.openprojects.net
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
prev parent reply other threads:[~2003-10-31 9:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-28 7:06 [LARTC] Explanation reqd. for few (more than few!) concepts in TC <long> Suraj Shankar
2003-10-28 18:08 ` Stef Coene
2003-10-28 18:08 ` Damjan
2003-10-29 14:23 ` Suraj Shankar
2003-10-29 15:02 ` Suraj Shankar
2003-10-29 15:07 ` Suraj Shankar
2003-10-29 18:41 ` Stef Coene
2003-10-29 18:59 ` Stef Coene
2003-10-30 5:54 ` Suraj Shankar
2003-10-30 6:10 ` Suraj Shankar
2003-10-30 10:38 ` Stef Coene
2003-10-30 10:43 ` Stef Coene
2003-10-31 7:23 ` Suraj Shankar
2003-10-31 9:47 ` Stef Coene [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=marc-lartc-106759372412293@msgid-missing \
--to=stef.coene@docum.org \
--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.