From: aruna.ramakrishna@oracle.com
To: Christoph Lameter <cl@linux.com>, Joonsoo Kim <iamjoonsoo.kim@lge.com>
Cc: Linux Memory Management List <linux-mm@kvack.org>,
LKML <linux-kernel@vger.kernel.org>,
Mike Kravetz <mike.kravetz@oracle.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH v2] mm/slab: Improve performance of gathering slabinfo stats
Date: Wed, 17 Aug 2016 00:13:41 -0700 [thread overview]
Message-ID: <57B40EA5.9040600@oracle.com> (raw)
In-Reply-To: <alpine.DEB.2.20.1608161052080.7887@east.gentwo.org>
On 08/16/2016 08:52 AM, Christoph Lameter wrote:
>
> On Tue, 16 Aug 2016, Joonsoo Kim wrote:
>
>> In SLUB, nr_slabs is manipulated without holding a lock so atomic
>> operation should be used.
>
> It could be moved under the node lock.
>
Christoph, Joonsoo,
I agree that nr_slabs could be common between SLAB and SLUB, but I think
that should be a separate patch, since converting nr_slabs to unsigned
long for SLUB will cause quite a bit of change in mm/slub.c that is not
related to adding counters to SLAB.
I'll send out an updated slab counters patch with Joonsoo's suggested
fix tomorrow (nr_slabs will be unsigned long for SLAB only, and there
will be a separate definition for SLUB), and once that's in, I'll create
a new patch that makes nr_slabs common for SLAB and SLUB, and also
converts total_objects to unsigned long. Maybe it can include some more
cleanup too. Does that sound acceptable?
Thanks,
Aruna
--
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:[~2016-08-17 7:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 19:01 [PATCH v2] mm/slab: Improve performance of gathering slabinfo stats Aruna Ramakrishna
2016-08-04 21:06 ` Andrew Morton
2016-08-04 21:49 ` Aruna Ramakrishna
2016-08-05 0:35 ` Joonsoo Kim
2016-08-05 14:21 ` Christoph Lameter
2016-08-16 3:03 ` Joonsoo Kim
2016-08-16 15:52 ` Christoph Lameter
2016-08-17 7:13 ` aruna.ramakrishna [this message]
2016-08-17 14:36 ` Christoph Lameter
2016-08-05 14:17 ` Christoph Lameter
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=57B40EA5.9040600@oracle.com \
--to=aruna.ramakrishna@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.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;
as well as URLs for NNTP newsgroup(s).