From: Christoph Lameter <cl@linux.com>
To: Wanpeng Li <liwanp@linux.vnet.ibm.com>
Cc: Pekka Enberg <penberg@kernel.org>, Matt Mackall <mpm@selenic.com>,
Glauber Costa <glommer@parallels.com>,
Andrew Morton <akpm@linux-foundation.org>,
Joonsoo Kim <js1304@gmail.com>,
David Rientjes <rientjes@google.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 3/5] mm/slab: Fix /proc/slabinfo unwriteable for slab
Date: Wed, 3 Jul 2013 13:55:20 +0000 [thread overview]
Message-ID: <0000013fa4d0e060-54cc0d26-3ddf-48bb-a868-1fb5b41ea5fb-000000@email.amazonses.com> (raw)
In-Reply-To: <1372812593-7617-3-git-send-email-liwanp@linux.vnet.ibm.com>
On Wed, 3 Jul 2013, Wanpeng Li wrote:
> Slab have some tunables like limit, batchcount, and sharedfactor can be
> tuned through function slabinfo_write. Commit (b7454ad3: mm/sl[au]b: Move
> slabinfo processing to slab_common.c) uncorrectly change /proc/slabinfo
> unwriteable for slab, this patch fix it by revert to original mode.
Acked-by: Christoph Lameter <cl@linux.com>
--
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 prev parent reply other threads:[~2013-07-03 13:55 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-03 0:49 [PATCH v2 1/5] mm/slab: Fix drain freelist excessively Wanpeng Li
2013-07-03 0:49 ` [PATCH v2 2/5] mm/slab: Sharing s_next and s_stop between slab and slub Wanpeng Li
2013-07-03 13:54 ` Christoph Lameter
2013-07-03 0:49 ` [PATCH v2 3/5] mm/slab: Fix /proc/slabinfo unwriteable for slab Wanpeng Li
2013-07-03 13:55 ` Christoph Lameter [this message]
2013-07-03 0:49 ` [PATCH v2 4/5] mm/slub: Drop unnecessary nr_partials Wanpeng Li
2013-07-03 13:59 ` Christoph Lameter
2013-07-03 0:49 ` [PATCH v2 5/5] mm/slub: Use node_nr_slabs and node_nr_objs in get_slabinfo Wanpeng Li
2013-07-03 13:54 ` [PATCH v2 1/5] mm/slab: Fix drain freelist excessively Christoph Lameter
2013-07-03 23:29 ` Wanpeng Li
2013-07-03 23:29 ` Wanpeng Li
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=0000013fa4d0e060-54cc0d26-3ddf-48bb-a868-1fb5b41ea5fb-000000@email.amazonses.com \
--to=cl@linux.com \
--cc=akpm@linux-foundation.org \
--cc=glommer@parallels.com \
--cc=js1304@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=liwanp@linux.vnet.ibm.com \
--cc=mpm@selenic.com \
--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