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: Re: [PATCH v2 0/3] move slabinfo processing to common code
Date: Fri, 19 Oct 2012 14:38:15 +0400 [thread overview]
Message-ID: <50812D97.9060004@parallels.com> (raw)
In-Reply-To: <1348844608-12568-1-git-send-email-glommer@parallels.com>
On 09/28/2012 07:03 PM, Glauber Costa wrote:
> 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
>
Hi
Any activity here ?
--
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>
WARNING: multiple messages have this Message-ID (diff)
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: Re: [PATCH v2 0/3] move slabinfo processing to common code
Date: Fri, 19 Oct 2012 14:38:15 +0400 [thread overview]
Message-ID: <50812D97.9060004@parallels.com> (raw)
In-Reply-To: <1348844608-12568-1-git-send-email-glommer@parallels.com>
On 09/28/2012 07:03 PM, Glauber Costa wrote:
> 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
>
Hi
Any activity here ?
next prev parent reply other threads:[~2012-10-19 10:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-28 15:03 [PATCH v2 0/3] move slabinfo processing to common code Glauber Costa
2012-09-28 15:03 ` Glauber Costa
2012-09-28 15:03 ` [PATCH v2 1/3] move slabinfo processing to slab_common.c Glauber Costa
2012-09-28 15:03 ` Glauber Costa
2012-09-28 15:03 ` [PATCH v2 2/3] move print_slabinfo_header " Glauber Costa
2012-09-28 15:03 ` 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 15:03 ` Glauber Costa
2012-09-28 16:26 ` Christoph Lameter
2012-09-28 16:26 ` Christoph Lameter
2012-10-19 10:38 ` Glauber Costa [this message]
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=50812D97.9060004@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 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.