From: Jarek Poplawski <jarkao2@gmail.com>
To: "Y. D." <duyuyang@gmail.com>
Cc: Patrick McHardy <kaber@trash.net>,
netdev <netdev@vger.kernel.org>,
netfilter-devel <netfilter-devel@vger.kernel.org>
Subject: Re: Re: IMQ bug: kernel reboot immediately
Date: Thu, 23 Apr 2009 12:46:49 +0000 [thread overview]
Message-ID: <20090423124649.GA7377@ff.dom.local> (raw)
In-Reply-To: <200904232028599062095@gmail.com>
On Thu, Apr 23, 2009 at 08:29:06PM +0800, Y. D. wrote:
>
> >I'd rather suggest to get rid of it and use ifb, AFAIK there hasn't
> >been a single version in all those years that didn't cause this kind
> >of problems.
> Thanks for your information.
>
> I just want to shape ingress traffic with my own qdisc, shoule it be IMQ or IFB.
> I am wondering where I can get a little detailed usage guide about IFB. ANY clue?
>
There is doc/actions/ifb-README in iproute2 sources. And google
as usual...
Jarek P.
next prev parent reply other threads:[~2009-04-23 12:46 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
2009-04-23 12:29 ` Y. D.
2009-04-23 12:46 ` Jarek Poplawski [this message]
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=20090423124649.GA7377@ff.dom.local \
--to=jarkao2@gmail.com \
--cc=duyuyang@gmail.com \
--cc=kaber@trash.net \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@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.