Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Ivan Pesin <ipesin@post.lviv.ua>
To: lartc@vger.kernel.org
Subject: [LARTC] imq crash investigation
Date: Wed, 17 Dec 2003 08:40:06 +0000	[thread overview]
Message-ID: <marc-lartc-107165245312033@msgid-missing> (raw)

Hello.

As you know Patrick McHardy stopped to support IMQ. As for now, this 
stuff has an annoying problem and I've made a little investigation of 
it. So, maybe it will be useful for someone.

First, pass all traffic of the interface (as in, as out) though imq 
device. Something like:

iptables -t mangle -I PREROUTING -i $DEV -j IMQ
iptables -t mangle -I POSTROUTING -o $DEV -j IMQ

This works ok. At least, after a day of running this setup seems to be 
stable. Now, lets attach a qdisc to imq:

RATE\x187
tc qdisc add dev imq0 handle 1: root tbf rate ${RATE}kbit \
     burst 15kb/8 limit 15kb

Ok, here it is. After some time (minutes,hours) I get a kernel panic.

As far as I know, IMQ is the _only_ way for now in Linux to limit the 
total bandwidth of the link (in+out). It would be excellent if somebody, 
  enough expirenced in kernel hacking, will be so kind to fix that problem.

Best regards,
   Ivan Pesin
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/

             reply	other threads:[~2003-12-17  8:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-17  8:40 Ivan Pesin [this message]
2003-12-17 15:16 ` [LARTC] imq crash investigation Roy
2003-12-17 16:43 ` Ivan Pesin
2003-12-17 21:32 ` Roy

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-107165245312033@msgid-missing \
    --to=ipesin@post.lviv.ua \
    --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