From: Glauber Costa <glommer@parallels.com>
To: linux-kernel@vger.kernel.org
Cc: linux-mm@kvack.org, Andrew Morton <akpm@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>,
Christoph Lameter <cl@linux.com>
Subject: [PATCH v2 0/3] move slabinfo processing to common code
Date: Fri, 28 Sep 2012 19:03:25 +0400 [thread overview]
Message-ID: <1348844608-12568-1-git-send-email-glommer@parallels.com> (raw)
Hi,
This patch moves on with the slab caches commonization, by moving
the slabinfo processing to common code in slab_common.c. It only touches
slub and slab, since slob doesn't create that file, which is protected
by a Kconfig switch.
Enjoy,
v2: return objects per slab and cache order in slabinfo structure as well
Glauber Costa (3):
move slabinfo processing to slab_common.c
move print_slabinfo_header to slab_common.c
sl[au]b: process slabinfo_show in common code
mm/slab.c | 118 ++++++++++++-------------------------------------------
mm/slab.h | 20 ++++++++++
mm/slab_common.c | 109 ++++++++++++++++++++++++++++++++++++++++++++++++++
mm/slub.c | 77 ++++++------------------------------
4 files changed, 166 insertions(+), 158 deletions(-)
--
1.7.11.4
--
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-28 15:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 15:03 Glauber Costa [this message]
2012-09-28 15:03 ` [PATCH v2 1/3] move slabinfo processing to slab_common.c Glauber Costa
2012-09-28 15:03 ` [PATCH v2 2/3] move print_slabinfo_header " Glauber Costa
2012-09-28 15:03 ` [PATCH v2 3/3] sl[au]b: process slabinfo_show in common code Glauber Costa
2012-09-28 16:26 ` Christoph Lameter
2012-10-19 10:38 ` [PATCH v2 0/3] move slabinfo processing to " 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=1348844608-12568-1-git-send-email-glommer@parallels.com \
--to=glommer@parallels.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
/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