From: Ezequiel Garcia <elezegarcia@gmail.com>
To: Pekka Enberg <penberg@kernel.org>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Cc: JoonSoo Kim <js1304@gmail.com>, Tim Bird <tim.bird@am.sony.com>,
Steven Rostedt <rostedt@goodmis.org>,
David Rientjes <rientjes@google.com>,
Christoph Lameter <cl@linux.com>,
Glauber Costa <glommer@parallels.com>
Subject: [PATCH v2 0/10] mm: SLxB cleaning and trace accuracy improvement
Date: Sat, 8 Sep 2012 17:49:47 -0300 [thread overview]
Message-ID: <CALF0-+VMtUPuLHg3CwDxFm-TjbN1=YavGO79Oo3GuymOLvikeA@mail.gmail.com> (raw)
Hi everyone,
This is the second spin of my patchset to clean SLxB and improve kmem
trace events accuracy.
For this v2, the most relevant stuff is:
I've dropped two patches that were not very well received:
Namely this two are now gone:
mm, slob: Use only 'ret' variable for both slob object and returned pointer
mm, slob: Trace allocation failures consistently
I believe consistency is important but perhaps this is just me being paranoid.
There's a lot of dumb movement and renaming. This might seem stupid
(and maybe it is) but it's necessary to create some common code between SLAB
and SLUB, and then factor it out.
Also, there's a patch to add a new option to disable gcc auto-inlining.
I know we hate to add new options, but this is necessary to get
accurate call site
traces. Plus, the option is in "Kernel Hacking", so it's for kernel
developers only.
This work is part of CELF Workgroup Project:
"Kernel_dynamic_memory_allocation_tracking_and_reduction" [1]
Feedback, comments, suggestions are very welcome.
Ezequiel Garcia (10):
mm: Factor SLAB and SLUB common code
mm, slub: Rename slab_alloc() -> slab_alloc_node() to match SLAB
mm, slab: Rename __cache_alloc() -> slab_alloc()
mm, slab: Match SLAB and SLUB kmem_cache_alloc_xxx_trace() prototype
mm, slab: Replace 'caller' type, void* -> unsigned long
mm, util: Use dup_user to duplicate user memory
mm, slob: Add support for kmalloc_track_caller()
mm, slab: Remove silly function slab_buffer_size()
mm, slob: Use NUMA_NO_NODE instead of -1
Makefile: Add option CONFIG_DISABLE_GCC_AUTOMATIC_INLINING
Makefile | 4 ++
include/linux/slab.h | 6 ++-
include/linux/slab_def.h | 14 ++---
include/linux/slob_def.h | 6 ++-
include/linux/slub_def.h | 2 +
lib/Kconfig.debug | 11 ++++
mm/slab.c | 122 +++++++++-------------------------------------
mm/slab_common.c | 57 +++++++++++++++++++++
mm/slob.c | 33 ++++++++++--
mm/slub.c | 55 +++------------------
mm/util.c | 11 +++-
11 files changed, 154 insertions(+), 167 deletions(-)
Thanks!
Ezequiel.
--
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-09-08 20:49 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-08 20:49 Ezequiel Garcia [this message]
2012-09-08 22:30 ` Christoph Lameter
2012-09-08 22:45 ` Ezequiel Garcia
2012-09-08 23:28 ` Christoph
2012-09-13 0:28 ` Ezequiel Garcia
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='CALF0-+VMtUPuLHg3CwDxFm-TjbN1=YavGO79Oo3GuymOLvikeA@mail.gmail.com' \
--to=elezegarcia@gmail.com \
--cc=cl@linux.com \
--cc=glommer@parallels.com \
--cc=js1304@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=rostedt@goodmis.org \
--cc=tim.bird@am.sony.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