From: Patrick McHardy <kaber@trash.net>
To: Salatiel Filho <salatiel.filho@gmail.com>
Cc: Denys Fedoryschenko <denys@visp.net.lb>,
Jan Engelhardt <jengelh@medozas.de>,
Jarek Poplawski <jarkao2@gmail.com>, "Y. D." <duyuyang@gmail.com>,
netdev <netdev@vger.kernel.org>,
netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: Re: IMQ bug: kernel reboot immediately
Date: Fri, 24 Apr 2009 17:29:05 +0200 [thread overview]
Message-ID: <49F1DAC1.5030809@trash.net> (raw)
In-Reply-To: <beb91d720904240823lf724b9bo207f4294dc9e4a8d@mail.gmail.com>
Salatiel Filho wrote:
> On Fri, Apr 24, 2009 at 12:19, Patrick McHardy <kaber@trash.net> wrote:
>> Salatiel Filho wrote:
>>> I am just curious , is there a qdisc in mainline that behaves similar
>>> to wrr [weight round robin] ?
>>> http://www.zz9.dk/wrr
>> DRR. But it can't do those strange load-balancing hacks.
>>
>
> what would it be those strange ugly hacks ? :)
Look at the code. At least they were there last time I had a look.
> Any good place where i can find DRR documentation/examples ?
No, but I can give you an example:
tc qdisc add dev <dev> parent <parent> handle <handle> drr
tc class add dev <dev> parent <handle> classid <classid> drr
repeat class add as often as you need. The default quantum per
class is the MTU, including link layer headers. You can manually
change that by specifying the "quantum" parameter for classes.
As for the flow classifier:
tc filter add dev <dev> protocol all pref 1 parent <handle> \
flow hash keys key1,key2,... divisor <number of classes>
The DRR classids need to be consequitive for this to work.
next prev parent reply other threads:[~2009-04-24 15:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-22 15:27 IMQ bug: kernel reboot immediately Y. D.
2009-04-23 8:43 ` Jarek Poplawski
2009-04-23 10:20 ` Patrick McHardy
2009-04-23 10:23 ` Jan Engelhardt
2009-04-23 10:28 ` Patrick McHardy
2009-04-23 11:12 ` Salatiel Filho
2009-04-23 11:22 ` Patrick McHardy
2009-04-23 11:40 ` Jarek Poplawski
2009-04-23 11:46 ` Patrick McHardy
2009-04-23 12:11 ` Jarek Poplawski
2009-04-23 12:13 ` Patrick McHardy
2009-04-23 12:37 ` Salatiel Filho
2009-04-23 12:41 ` Patrick McHardy
2009-04-23 23:32 ` Salatiel Filho
2009-04-24 14:49 ` Patrick McHardy
2009-04-24 14:55 ` Denys Fedoryschenko
2009-04-24 15:14 ` Salatiel Filho
2009-04-24 15:19 ` Patrick McHardy
2009-04-24 15:23 ` Salatiel Filho
2009-04-24 15:29 ` Patrick McHardy [this message]
2009-04-23 12:29 ` Y. D.
2009-04-23 12:46 ` Jarek Poplawski
2009-05-02 12:03 ` pud
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=49F1DAC1.5030809@trash.net \
--to=kaber@trash.net \
--cc=denys@visp.net.lb \
--cc=duyuyang@gmail.com \
--cc=jarkao2@gmail.com \
--cc=jengelh@medozas.de \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=salatiel.filho@gmail.com \
/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).