From: "Manfred Spraul" <manfred@colorfullife.com>
To: <frank@unternet.org>
Cc: "Alexander Viro" <viro@math.psu.edu>, <linux-kernel@vger.kernel.org>
Subject: Re: Severe trashing in 2.4.4
Date: Mon, 30 Apr 2001 00:06:52 +0200 [thread overview]
Message-ID: <001001c0d0f8$bf5ec5e0$5517fea9@local> (raw)
> On Sun, Apr 29, 2001 at 01:58:52PM -0400, Alexander Viro wrote:
> > Hmm... I'd say that you also have a leak in kmalloc()'ed stuff -
> > something in 1K--2K range. From your logs it looks like the
> > thing never shrinks and grows prettu fast...
You could enable STATS in mm/slab.c, then the number of alloc and free
calls would be printed in /proc/slabinfo.
> Yeah, those as well. I kinda guessed they were related...
Could you check /proc/sys/net/core/hot_list_length and skb_head_pool
(not available in /proc, use gdb --core /proc/kcore)? I doubt that this
causes your problems, but the skb_head code uses a special per-cpu
linked list for even faster allocations.
Which network card do you use? Perhaps a bug in the zero-copy code of
the driver?
--
Manfred
next reply other threads:[~2001-04-29 22:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-29 22:06 Manfred Spraul [this message]
2001-04-29 22:14 ` Severe trashing in 2.4.4 Frank de Lange
[not found] <200104290311.f3T3BeO09131@bellini.kjist.ac.kr>
[not found] ` <20010429140155.D24432@unternet.org>
[not found] ` <3AEC09EE.342FE1C8@kjist.ac.kr>
[not found] ` <20010429152414.B11395@athlon.random>
2001-04-29 16:18 ` Frank de Lange
2001-04-29 16:27 ` Alexander Viro
2001-04-29 17:46 ` Frank de Lange
2001-04-29 17:58 ` Alexander Viro
2001-04-29 18:01 ` Frank de Lange
2001-04-29 18:04 ` Frank de Lange
2001-04-30 7:45 ` Mike Galbraith
2001-04-30 6:15 ` Mike Galbraith
[not found] ` <200104291911.XAA04489@ms2.inr.ac.ru>
[not found] ` <20010429214853.G11681@unternet.org>
[not found] ` <15084.42876.515254.47471@pizda.ninka.net>
2001-04-30 0:24 ` Frank de Lange
2001-04-30 2:00 ` David S. Miller
-- strict thread matches above, loose matches on Subject: below --
2001-04-28 18:24 Frank de Lange
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='001001c0d0f8$bf5ec5e0$5517fea9@local' \
--to=manfred@colorfullife.com \
--cc=frank@unternet.org \
--cc=linux-kernel@vger.kernel.org \
--cc=viro@math.psu.edu \
/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.