From: Joonsoo Kim <js1304@gmail.com>
To: Greg Thelen <gthelen@google.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Christoph Lameter <cl@linux.com>,
Pekka Enberg <penberg@kernel.org>,
David Rientjes <rientjes@google.com>,
Vladimir Davydov <vdavydov.dev@gmail.com>,
linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] slab: avoid IPIs when creating kmem caches
Date: Mon, 17 Apr 2017 11:07:14 +0900 [thread overview]
Message-ID: <20170417020712.GB1351@js1304-desktop> (raw)
In-Reply-To: <20170416214544.109476-1-gthelen@google.com>
On Sun, Apr 16, 2017 at 02:45:44PM -0700, Greg Thelen wrote:
> Each slab kmem cache has per cpu array caches. The array caches are
> created when the kmem_cache is created, either via kmem_cache_create()
> or lazily when the first object is allocated in context of a kmem
> enabled memcg. Array caches are replaced by writing to /proc/slabinfo.
>
> Array caches are protected by holding slab_mutex or disabling
> interrupts. Array cache allocation and replacement is done by
> __do_tune_cpucache() which holds slab_mutex and calls
> kick_all_cpus_sync() to interrupt all remote processors which confirms
> there are no references to the old array caches.
>
> IPIs are needed when replacing array caches. But when creating a new
> array cache, there's no need to send IPIs because there cannot be any
> references to the new cache. Outside of memcg kmem accounting these
> IPIs occur at boot time, so they're not a problem. But with memcg kmem
> accounting each container can create kmem caches, so the IPIs are
> wasteful.
>
> Avoid unnecessary IPIs when creating array caches.
>
> Test which reports the IPI count of allocating slab in 10000 memcg:
> import os
>
> def ipi_count():
> with open("/proc/interrupts") as f:
> for l in f:
> if 'Function call interrupts' in l:
> return int(l.split()[1])
>
> def echo(val, path):
> with open(path, "w") as f:
> f.write(val)
>
> n = 10000
> os.chdir("/mnt/cgroup/memory")
> pid = str(os.getpid())
> a = ipi_count()
> for i in range(n):
> os.mkdir(str(i))
> echo("1G\n", "%d/memory.limit_in_bytes" % i)
> echo("1G\n", "%d/memory.kmem.limit_in_bytes" % i)
> echo(pid, "%d/cgroup.procs" % i)
> open("/tmp/x", "w").close()
> os.unlink("/tmp/x")
> b = ipi_count()
> print "%d loops: %d => %d (+%d ipis)" % (n, a, b, b-a)
> echo(pid, "cgroup.procs")
> for i in range(n):
> os.rmdir(str(i))
>
> patched: 10000 loops: 1069 => 1170 (+101 ipis)
> unpatched: 10000 loops: 1192 => 48933 (+47741 ipis)
>
> Signed-off-by: Greg Thelen <gthelen@google.com>
Acked-by: Joonsoo Kim <iamjoonsoo.kim@lge.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:[~2017-04-17 2:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-16 21:45 Greg Thelen
2017-04-17 2:07 ` Joonsoo Kim [this message]
2017-04-17 22:25 ` 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=20170417020712.GB1351@js1304-desktop \
--to=js1304@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=cl@linux.com \
--cc=gthelen@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=vdavydov.dev@gmail.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