From: svc_lmoiseichuk@magicleap.com
To: hannes@cmpxchg.org, mhocko@kernel.org, vdavydov.dev@gmail.com,
tj@kernel.org, lizefan@huawei.com, cgroups@vger.kernel.org
Cc: akpm@linux-foundation.org, rientjes@google.com,
minchan@kernel.org, vinmenon@codeaurora.org,
andriy.shevchenko@linux.intel.com, penberg@kernel.org,
linux-mm@kvack.org, Leonid Moiseichuk <lmoiseichuk@magicleap.com>
Subject: [PATCH v1 0/2] memcg, vmpressure: expose vmpressure controls
Date: Tue, 14 Apr 2020 13:18:38 -0400 [thread overview]
Message-ID: <20200414171840.22053-1-lmoiseichuk@magicleap.com> (raw)
From: Leonid Moiseichuk <lmoiseichuk@magicleap.com>
Small tweak to populate vmpressure parameters to userspace without
any built-in logic change.
The vmpressure is used actively (e.g. on Android) to track mm stress.
vmpressure parameters selected empiricaly quite long time ago and not
always suitable for modern memory configurations. Modern 8 GB devices
starts triggering medium threshold when about 3 GB memory not used,
and situation with 12 and 16 GB devices even worse.
Testing performed:
* Build kernel for x86-64 and aarch64 (Tegra X2 SoC)
* Booted and checked that all properties published
* Tuned settings and observed adequate response
* sysbench and memory bubble application (memsize from lmbench)
used to verify reactions
Change Log:
v1:
=> updated commit with 8 GB numbers per Michal Hocko request
v0:
=> initial implementation
=> tested on x86-64 and aarch64
Leonid Moiseichuk (2):
memcg, vmpressure: expose vmpressure controls
memcg, vmpressure: expose vmpressure controls
.../admin-guide/cgroup-v1/memory.rst | 12 +-
include/linux/vmpressure.h | 35 ++++++
mm/memcontrol.c | 113 ++++++++++++++++++
mm/vmpressure.c | 101 +++++++---------
4 files changed, 200 insertions(+), 61 deletions(-)
--
2.17.1
next reply other threads:[~2020-04-14 18:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-14 17:18 svc_lmoiseichuk [this message]
2020-04-14 17:18 ` [PATCH v1 1/2] memcg, vmpressure: expose vmpressure controls svc_lmoiseichuk
2020-04-14 17:18 ` [PATCH v1 2/2] " svc_lmoiseichuk
2020-04-14 18:35 ` [PATCH v1 0/2] " Michal Hocko
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=20200414171840.22053-1-lmoiseichuk@magicleap.com \
--to=svc_lmoiseichuk@magicleap.com \
--cc=akpm@linux-foundation.org \
--cc=andriy.shevchenko@linux.intel.com \
--cc=cgroups@vger.kernel.org \
--cc=hannes@cmpxchg.org \
--cc=linux-mm@kvack.org \
--cc=lizefan@huawei.com \
--cc=lmoiseichuk@magicleap.com \
--cc=mhocko@kernel.org \
--cc=minchan@kernel.org \
--cc=penberg@kernel.org \
--cc=rientjes@google.com \
--cc=tj@kernel.org \
--cc=vdavydov.dev@gmail.com \
--cc=vinmenon@codeaurora.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;
as well as URLs for NNTP newsgroup(s).