From: Geert Premereur Geert.Premereur@inno.com
To: lartc@vger.kernel.org
Subject: [LARTC] Priorities
Date: Sun, 28 Jan 2001 21:15:53 +0000 [thread overview]
Message-ID: <marc-lartc-98373940416921@msgid-missing> (raw)
<PRE>Hi,
I have been experimenting with linux bandwidth shaping through tc. Basically
everything works fine, but because of the somewhat scarce and scattered
documentation (I looked through the howto and the mailing list archives (and
even in the kernel sources)) I still have some questions, probably like most
of us ;-)
What is the exact effect of setting a priority for a class?
e.g. tc class add dev eth1 ... cbq prio 1 ...
vs. tc class add dev eth1 ... cbq prio 8 ...
with all other cbq parameters the same, results in having the first class
consistently allocated only 1% more bandwidth. This difference is much less
than what one would expect. It seems related to the prio parameter however,
because it is independent of the order the classes are specified.
So what's up? When are those priorities used? Do I need to set other
parameters or queues/classes as well? I tried to attach other queues than
the default to the classes (prio for instance), but that didn't help. The
top level queue is a CBQ
Maybe my method of testing is flawed? I use a program 'ttcp' that
continuously sends maximum size TCP packets to a given port.
Thanks,
Geert
</PRE>
reply other threads:[~2001-01-28 21:15 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=marc-lartc-98373940416921@msgid-missing \
--to=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.