From: Pekka Enberg <penberg@gmail.com>
To: Baruch Even <baruch@ev-en.org>
Cc: Matt Mackall <mpm@selenic.com>,
linux-kernel <linux-kernel@vger.kernel.org>,
penberg@cs.helsinki.fi
Subject: Re: [PATCH] /proc/kmalloc
Date: Mon, 21 Feb 2005 15:53:19 +0200 [thread overview]
Message-ID: <84144f0205022105532bad35f7@mail.gmail.com> (raw)
In-Reply-To: <42194AE0.2040209@ev-en.org>
On Mon, 21 Feb 2005 02:43:44 +0000, Baruch Even <baruch@ev-en.org> wrote:
> One thing I've seen once that might be worth adding is the ability to
> mark generations and then ask "what allocations exist from generation x?".
In less general terms, I would like to see which module made the
allocation so after doing rmmod I could see if the module leaks
memory. Many subsystems are already doing this by intercepting
kmalloc() and kfree() calls so it would be nice to get rid of the
duplication...
Pekka
prev parent reply other threads:[~2005-02-21 13:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-20 20:47 [PATCH] /proc/kmalloc Matt Mackall
2005-02-20 21:59 ` Arnd Bergmann
2005-02-21 2:43 ` Baruch Even
2005-02-21 13:53 ` Pekka Enberg [this message]
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=84144f0205022105532bad35f7@mail.gmail.com \
--to=penberg@gmail.com \
--cc=baruch@ev-en.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mpm@selenic.com \
--cc=penberg@cs.helsinki.fi \
/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