From: Andrew Morton <akpm@linux-foundation.org>
To: David Rientjes <rientjes@google.com>
Cc: Greg Thelen <gthelen@google.com>,
Aruna Ramakrishna <aruna.ramakrishna@oracle.com>,
Christoph Lameter <cl@linux.com>,
Joonsoo Kim <iamjoonsoo.kim@lge.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [patch] mm, slab: faster active and free stats
Date: Tue, 8 Nov 2016 15:17:27 -0800 [thread overview]
Message-ID: <20161108151727.b64035da825c69bced88b46d@linux-foundation.org> (raw)
In-Reply-To: <alpine.DEB.2.10.1611081505240.13403@chino.kir.corp.google.com>
On Tue, 8 Nov 2016 15:06:45 -0800 (PST) David Rientjes <rientjes@google.com> wrote:
> Reading /proc/slabinfo or monitoring slabtop(1) can become very expensive
> if there are many slab caches and if there are very lengthy per-node
> partial and/or free lists.
>
> Commit 07a63c41fa1f ("mm/slab: improve performance of gathering slabinfo
> stats") addressed the per-node full lists which showed a significant
> improvement when no objects were freed. This patch has the same
> motivation and optimizes the remainder of the usecases where there are
> very lengthy partial and free lists.
>
> This patch maintains per-node active_slabs (full and partial) and
> free_slabs rather than iterating the lists at runtime when reading
> /proc/slabinfo.
Are there any nice numbers you can share?
next prev parent reply other threads:[~2016-11-08 23:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-08 23:06 [patch] mm, slab: faster active and free stats David Rientjes
2016-11-08 23:17 ` Andrew Morton [this message]
2016-11-10 0:38 ` David Rientjes
2016-11-11 5:53 ` Joonsoo Kim
2016-11-11 10:30 ` David Rientjes
2016-11-28 7:40 ` Joonsoo Kim
2016-11-30 0:56 ` David Rientjes
2016-12-02 7:58 ` 김준수/선임연구원/SW Platform(연)AOT팀(iamjoonsoo.kim@lge.com)
2016-12-05 4:23 ` [patch -mm] mm, slab: maintain total slab count instead of active count David Rientjes
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=20161108151727.b64035da825c69bced88b46d@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=aruna.ramakrishna@oracle.com \
--cc=cl@linux.com \
--cc=gthelen@google.com \
--cc=iamjoonsoo.kim@lge.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.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).