From: Andy Whitcroft <apw@shadowen.org>
To: Pekka Enberg <penberg@cs.helsinki.fi>
Cc: Christoph Hellwig <hch@lst.de>, netdev@oss.sgi.com, linux-mm@kvack.org
Subject: Re: [PATCH 1/3]: leak tracking for kmalloc node
Date: Wed, 08 Nov 2006 14:20:05 +0000 [thread overview]
Message-ID: <4551E795.3090805@shadowen.org> (raw)
In-Reply-To: <84144f020610300632i799214a6p255e1690a93a95d4@mail.gmail.com>
Pekka Enberg wrote:
> Hi,
>
> On 10/30/06, Christoph Hellwig <hch@lst.de> wrote:
>> If we want to use the node-aware kmalloc in __alloc_skb we need
>> the tracker is responsible for leak tracking magic for it. This
>> patch implements it. The code is far too ugly for my taste, but it's
>> doing exactly what the regular kmalloc is doing and thus follows it's
>> style.
>
> Yeah, the allocation paths are ugly. If only someone with NUMA machine
> could give this a shot so we can get it merged:
>
> http://marc.theaimsgroup.com/?l=linux-kernel&m=115952740803511&w=2
>
> Should clean up NUMA kmalloc tracking too.
I can give this a test, what is it based on...
-apw
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
next prev parent reply other threads:[~2006-11-08 14:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 14:14 [PATCH 1/3]: leak tracking for kmalloc node Christoph Hellwig
2006-10-30 14:32 ` Pekka Enberg
2006-10-30 14:52 ` Christoph Hellwig
2006-11-08 14:20 ` Andy Whitcroft [this message]
2006-11-08 14:29 ` Pekka Enberg
2006-11-08 14:54 ` Pekka J Enberg
2006-11-08 16:04 ` Andy Whitcroft
-- strict thread matches above, loose matches on Subject: below --
2006-11-15 17:36 [PATCH 1/3] leak tracking for kmalloc_node Christoph Hellwig
2006-11-15 17:36 ` Christoph Hellwig
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=4551E795.3090805@shadowen.org \
--to=apw@shadowen.org \
--cc=hch@lst.de \
--cc=linux-mm@kvack.org \
--cc=netdev@oss.sgi.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 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.