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: CK5 [6/6] Common alignment code
Date: Thu, 29 Nov 2012 13:42:22 +0400 [thread overview]
Message-ID: <50B72DFE.2040209@parallels.com> (raw)
In-Reply-To: <0000013b47d45710-368fdf96-d763-43ad-b670-3cade26ebd9e-000000@email.amazonses.com>
On 11/28/2012 08:23 PM, Christoph Lameter wrote:
> Extract the code to do object alignment from the allocators.
> Do the alignment calculations in slab_common so that the
> __kmem_cache_create functions of the allocators do not have
> to deal with alignment.
>
> Signed-off-by: Christoph Lameter <cl@linux.com>
Looks decent and straightforward enough.
Reviewed-by: Glauber Costa <glommer@parallels.com>
--
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>
prev parent reply other threads:[~2012-11-29 9:42 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20121128162238.111670741@linux.com>
2012-11-28 16:23 ` CK5 [1/6] Use correct cpu_slab on dead cpu Christoph Lameter
2012-11-28 16:23 ` CK5 [2/6] slab: Simplify bootstrap Christoph Lameter
2012-11-28 16:23 ` CK5 [3/6] create common functions for boot slab creation Christoph Lameter
2012-11-28 16:23 ` CK5 [4/6] slub: Use a statically allocated kmem_cache boot structure for bootstrap Christoph Lameter
2012-11-28 16:23 ` CK5 [5/6] slab: Use the new create_boot_cache function to simplify bootstrap Christoph Lameter
2012-11-29 9:38 ` Glauber Costa
2012-11-28 16:23 ` CK5 [6/6] Common alignment code Christoph Lameter
2012-11-29 9:42 ` Glauber Costa [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=50B72DFE.2040209@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.