From: Glauber Costa <glommer@parallels.com>
To: linux-mm@kvack.org
Cc: linux-kernel@vger.kernel.org, Joonsoo Kim <js1304@gmail.com>,
David Rientjes <rientjes@google.com>,
Pekka Enberg <penberg@kernel.org>,
Christoph Lameter <cl@linux.com>
Subject: [PATCH v2 0/2] common entry point for kmem_cache_free
Date: Wed, 24 Oct 2012 17:59:16 +0400 [thread overview]
Message-ID: <1351087158-8524-1-git-send-email-glommer@parallels.com> (raw)
The goal of this patchset is to provide a single entry point for
kmem_cache_free. Other functions, such as the allocation itself, and kmalloc
could easily follow.
The main problem here, is that if we keep the allocator-specific functions
in their .c file, we lose the ability to inline their fast paths. Being this
such a critical path, we would like to keep doing so.
During the last discussion around this (https://lkml.org/lkml/2012/10/22/639),
JoonSoo Kim suggested that we could achieve this by just including the
allocator-specific .c files in slab_common.c, a suggestion I considered but
quickly disregarding fearing a quite ugly end result.
Turns out it doesn't look so bad. So please let me know what you think.
Thanks
Glauber Costa (2):
kmem_cache: include allocators code directly into slab_common
slab: move kmem_cache_free to common code
mm/Makefile | 3 ---
mm/slab.c | 23 ++---------------------
mm/slab_common.c | 50 ++++++++++++++++++++++++++++++++++++++++++++++++++
mm/slob.c | 11 ++++-------
mm/slub.c | 5 +----
5 files changed, 57 insertions(+), 35 deletions(-)
--
1.7.11.7
--
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 reply other threads:[~2012-10-24 13:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-24 13:59 Glauber Costa [this message]
2012-10-24 13:59 ` [PATCH v2 1/2] kmem_cache: include allocators code directly into slab_common Glauber Costa
2012-10-24 14:29 ` Christoph Lameter
2012-10-24 14:35 ` Glauber Costa
2012-10-24 17:29 ` JoonSoo Kim
2012-10-24 15:33 ` Andi Kleen
2012-10-24 18:02 ` Pekka Enberg
2012-10-24 19:34 ` Christoph Lameter
2012-10-26 14:15 ` JoonSoo Kim
2012-10-30 15:31 ` Christoph Lameter
2012-10-30 15:35 ` Glauber Costa
2012-10-30 20:27 ` Andi Kleen
2012-10-24 13:59 ` [PATCH v2 2/2] slab: move kmem_cache_free to common code Glauber Costa
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=1351087158-8524-1-git-send-email-glommer@parallels.com \
--to=glommer@parallels.com \
--cc=cl@linux.com \
--cc=js1304@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox