linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Michal Hocko <mhocko@kernel.org>
To: svc_lmoiseichuk@magicleap.com
Cc: hannes@cmpxchg.org, vdavydov.dev@gmail.com, tj@kernel.org,
	lizefan@huawei.com, cgroups@vger.kernel.org,
	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: Re: [PATCH v1 0/2] memcg, vmpressure: expose vmpressure controls
Date: Tue, 14 Apr 2020 20:35:41 +0200	[thread overview]
Message-ID: <20200414183541.GS4629@dhcp22.suse.cz> (raw)
In-Reply-To: <20200414171840.22053-1-lmoiseichuk@magicleap.com>

On Tue 14-04-20 13:18:38, svc_lmoiseichuk@magicleap.com wrote:
> 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.

I am sorry but this doesn't answer questions I've had for the previous
version of the patch. Please do not post newer versions until there is a
consensusn on the approach based on the review feedback. In order to not
fragment the discussion, let's continue in the original email thread
http://lkml.kernel.org/r/20200413215750.7239-1-lmoiseichuk@magicleap.com
-- 
Michal Hocko
SUSE Labs


      parent reply	other threads:[~2020-04-14 18:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-14 17:18 [PATCH v1 0/2] memcg, vmpressure: expose vmpressure controls svc_lmoiseichuk
2020-04-14 17:18 ` [PATCH v1 1/2] " svc_lmoiseichuk
2020-04-14 17:18 ` [PATCH v1 2/2] " svc_lmoiseichuk
2020-04-14 18:35 ` Michal Hocko [this message]

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=20200414183541.GS4629@dhcp22.suse.cz \
    --to=mhocko@kernel.org \
    --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=minchan@kernel.org \
    --cc=penberg@kernel.org \
    --cc=rientjes@google.com \
    --cc=svc_lmoiseichuk@magicleap.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).