From: Christoph Lameter <cl@linux.com>
To: Glauber Costa <glommer@parallels.com>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Andrew Morton <akpm@linux-foundation.org>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>
Subject: Re: [PATCH 0/4] move slabinfo processing to common code
Date: Thu, 27 Sep 2012 14:48:27 +0000 [thread overview]
Message-ID: <0000013a0833408c-117f7b98-4f5f-4db8-a3a3-1b9ca2ff1ce8-000000@email.amazonses.com> (raw)
In-Reply-To: <1348756660-16929-1-git-send-email-glommer@parallels.com>
On Thu, 27 Sep 2012, Glauber Costa wrote:
> 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.
Thanks. That was also something on my todo list.
--
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-09-27 14:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 14:37 Glauber Costa
2012-09-27 14:37 ` [PATCH 1/4] sl[au]b: move slabinfo processing to slab_common.c Glauber Costa
2012-09-27 14:50 ` Christoph Lameter
2012-09-27 14:37 ` [PATCH 2/4] sl[au]b: move print_slabinfo_header " Glauber Costa
2012-09-27 14:51 ` Christoph Lameter
2012-09-27 14:37 ` [PATCH 3/4] slub: move slub internal functions to its header Glauber Costa
2012-09-27 14:53 ` Christoph Lameter
2012-09-27 14:37 ` [PATCH 4/4] sl[au]b: process slabinfo_show in common code Glauber Costa
2012-09-27 15:07 ` Christoph Lameter
2012-09-27 16:38 ` Glauber Costa
2012-09-27 17:53 ` Christoph Lameter
2012-09-27 14:48 ` Christoph Lameter [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=0000013a0833408c-117f7b98-4f5f-4db8-a3a3-1b9ca2ff1ce8-000000@email.amazonses.com \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=glommer@parallels.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