From: Glauber Costa <glommer@parallels.com>
To: Christoph Lameter <cl@linux.com>
Cc: Pekka Enberg <penberg@kernel.org>, Joonsoo Kim <js1304@gmail.com>,
linux-mm@kvack.org, David Rientjes <rientjes@google.com>,
elezegarcia@gmail.com
Subject: Re: CK4 [00/15] Sl[auo]b: Common kmalloc caches V4
Date: Mon, 29 Oct 2012 17:36:17 +0400 [thread overview]
Message-ID: <508E8651.1080809@parallels.com> (raw)
In-Reply-To: <0000013a934eed6d-a9c1b247-dbbc-485d-b7cf-89aa36dcca57-000000@email.amazonses.com>
On 10/24/2012 07:05 PM, Christoph Lameter wrote:
> V3->V4:
> - Further fixes of issues pointed out by Joonsoo and Glauber.
>
> V2-V3:
> - Further cleanup and reordering as suggested by Glauber
>
> V1-V2:
> - Clean up numerous things as suggested by Glauber.
> - Add two more patches that extract more kmalloc stuff
> into common files.
>
> This patchset cleans up the bootstrap of the allocators
> and creates a common functions to handle the kmalloc
> array. The results are more common data structures and
> functions that will simplify further work
> on having common functions for all allocators.
>
> This patchset is against Pekka's slab/next tree as of today.
It looks good to me.
--
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:[~2012-10-29 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 15:05 CK4 [00/15] Sl[auo]b: Common kmalloc caches V4 Christoph Lameter
2012-10-29 13:36 ` Glauber Costa [this message]
2012-11-01 13:40 ` Ezequiel Garcia
2012-11-01 20:24 ` Christoph Lameter
2012-11-01 20:35 ` Ezequiel Garcia
2012-11-01 21:03 ` Christoph Lameter
2012-11-01 21:18 ` Ezequiel Garcia
2012-11-01 21:46 ` Christoph Lameter
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=508E8651.1080809@parallels.com \
--to=glommer@parallels.com \
--cc=cl@linux.com \
--cc=elezegarcia@gmail.com \
--cc=js1304@gmail.com \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.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.