From: Roman Gushchin <guro@fb.com>
To: "lsf-pc@lists.linux-foundation.org" <lsf-pc@lists.linux-foundation.org>
Cc: "linux-mm@kvack.org" <linux-mm@kvack.org>
Subject: [LSF/MM/BPF TOPIC] kernel memory accounting
Date: Wed, 15 Jan 2020 23:29:45 +0000 [thread overview]
Message-ID: <20200115232941.GA3229@xps.dhcp.thefacebook.com> (raw)
I'm currently working on the new cgroup slab controller [1], which
fundamentally changes how the slab memory is tracked: instead of
creating a separate set of kmem_caches for each memory cgroup a
single global set is used for all non-root allocations. Memcg
ownership is then tracked per-object rather than per-page.
The new approach comes with a much better slab utilization and
allows to reduce the slab memory size by up to ~40%.
It's also creates a foundation for tracking other objects which
aren't page-sized: e.g. percpu allocations, which are scattered
over multiple pages.
I'd like to share latest results and discuss all ongoing questions,
concerns and suggestions.
[1] https://lkml.org/lkml/2019/10/17/1065
reply other threads:[~2020-01-15 23:30 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20200115232941.GA3229@xps.dhcp.thefacebook.com \
--to=guro@fb.com \
--cc=linux-mm@kvack.org \
--cc=lsf-pc@lists.linux-foundation.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox