From: Jarek Poplawski <jarkao2@gmail.com>
To: Eric Dumazet <eric.dumazet@gmail.com>
Cc: Anand Raj Manickam <anandrm@gmail.com>,
netdev@vger.kernel.org, netfilter-devel@vger.kernel.org,
shemminger@vyatta.com
Subject: Re: Kernel Panic on OOM with 10 HTB rules
Date: Wed, 08 Sep 2010 19:25:36 +0200 [thread overview]
Message-ID: <4C87C710.8080804@gmail.com> (raw)
In-Reply-To: <1283957137.2748.71.camel@edumazet-laptop>
Eric Dumazet wrote, On 09/08/2010 04:45 PM:
> Le mercredi 08 septembre 2010 à 19:39 +0530, Anand Raj Manickam a
> écrit :
>>
>> imq0 Link encap:UNSPEC HWaddr
>> 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
>> UP RUNNING NOARP MTU:16000 Metric:1
>> RX packets:129112 errors:0 dropped:0 overruns:0 frame:0
>> TX packets:129114 errors:0 dropped:0 overruns:0 carrier:0
>> collisions:0 txqueuelen:11000
>> RX bytes:31060964 (29.6 MiB) TX bytes:31062207 (29.6 MiB)
>>
> If you cannot switch to 64bit kernel, then you are forced to use lower
> queue lengths (I see your imq devices use insane 11000 txqueuelen)
>
> Each frame use 4K, maybe 16K, it depends on MTU.
>
> even if we dont take into account other needs :
> 11000 * 16K = 170 Mbytes per imqX
> 1000 * 4K = 4Mbytes per ethX
>
> 170M * 8 -> memory overflow
>
You should consider that htb creates by default one queue per class
with txqueuelen limit each. This should probably explain why your
problems start when you classify to many classes.
Jarek P.
next prev parent reply other threads:[~2010-09-08 17:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-09-08 10:52 Kernel Panic on OOM with 10 HTB rules Anand Raj Manickam
2010-09-08 12:42 ` Eric Dumazet
2010-09-08 14:09 ` Anand Raj Manickam
2010-09-08 14:45 ` Eric Dumazet
2010-09-08 15:02 ` Krzysztof Olędzki
2010-09-08 17:25 ` Jarek Poplawski [this message]
2010-09-16 9:35 ` Patrick McHardy
2010-09-16 12:20 ` Anand Raj Manickam
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=4C87C710.8080804@gmail.com \
--to=jarkao2@gmail.com \
--cc=anandrm@gmail.com \
--cc=eric.dumazet@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=netfilter-devel@vger.kernel.org \
--cc=shemminger@vyatta.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 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.