From: Manfred Spraul <manfred@colorfullife.com>
To: Alexander Nyberg <alexn@telia.com>
Cc: Andrew Morton <akpm@osdl.org>, linux-kernel@vger.kernel.org
Subject: Re: Patch for slab leak debugging
Date: Sat, 09 Jul 2005 10:58:05 +0200 [thread overview]
Message-ID: <42CF919D.40009@colorfullife.com> (raw)
In-Reply-To: <1120898643.1171.4.camel@localhost.localdomain>
Alexander Nyberg wrote:
>Yeah I knew there was one, but I thought that was a standalone patch
>(the one turning all bufctl to unsigned long, turning off irqs and
>printing all slabs_full to console), my intention with this was a
>proper /proc entry, something that could be a simple config option.
>
>
>
No, I never wrote a proper /proc interface. But I think the bufctl
approach is the better solution than storing the first 5 entries in the
slab structure:
What if there is a leak on a cache with more than 5 entries per slab?
--
Manfred
next prev parent reply other threads:[~2005-07-09 8:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-08 20:56 Patch for slab leak debugging Alexander Nyberg
2005-07-08 23:52 ` Andrew Morton
2005-07-08 23:55 ` Andrew Morton
2005-07-09 8:44 ` Alexander Nyberg
2005-07-09 8:58 ` Manfred Spraul [this message]
2005-07-09 10:26 ` Alexander Nyberg
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=42CF919D.40009@colorfullife.com \
--to=manfred@colorfullife.com \
--cc=akpm@osdl.org \
--cc=alexn@telia.com \
--cc=linux-kernel@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