From: Konstantin Khlebnikov <khlebnikov@yandex-team.ru>
To: Michal Hocko <mhocko@kernel.org>
Cc: linux-mm@kvack.org, linux-kernel@vger.kernel.org,
Vladimir Davydov <vdavydov.dev@gmail.com>,
Johannes Weiner <hannes@cmpxchg.org>, Tejun Heo <tj@kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Mel Gorman <mgorman@techsingularity.net>,
Roman Gushchin <guro@fb.com>,
linux-api@vger.kernel.org
Subject: Re: [PATCH RFC] mm/madvise: implement MADV_STOCKPILE (kswapd from user space)
Date: Mon, 27 May 2019 17:30:31 +0300 [thread overview]
Message-ID: <e17e1370-9e88-e50c-94e3-736c122c1baf@yandex-team.ru> (raw)
In-Reply-To: <20190527142156.GE1658@dhcp22.suse.cz>
On 27.05.2019 17:21, Michal Hocko wrote:
> On Mon 27-05-19 16:12:23, Michal Hocko wrote:
>> [Cc linux-api. Please always cc this list when proposing a new user
>> visible api. Keeping the rest of the email intact for reference]
>>
>> On Mon 27-05-19 13:05:58, Konstantin Khlebnikov wrote:
> [...]
>>> This implements manual kswapd-style memory reclaim initiated by userspace.
>>> It reclaims both physical memory and cgroup pages. It works in context of
>>> task who calls syscall madvise thus cpu time is accounted correctly.
>
> I do not follow. Does this mean that the madvise always reclaims from
> the memcg the process is member of?
>
First it reclaims in its own memcg while limit - usage < requested.
Then repeats this in parent memcg and so on. And at least pokes global
direct reclaimer while system wide free memory is less than requested.
So, if machine is divided into containers without overcommit global
reclaim will never happens - memcg will free enough memory.
next prev parent reply other threads:[~2019-05-27 14:30 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-27 10:05 Konstantin Khlebnikov
2019-05-27 14:12 ` Michal Hocko
2019-05-27 14:21 ` Michal Hocko
2019-05-27 14:30 ` Konstantin Khlebnikov [this message]
2019-05-27 14:39 ` Michal Hocko
2019-05-28 6:25 ` Konstantin Khlebnikov
2019-05-28 6:51 ` Michal Hocko
2019-05-28 7:30 ` Konstantin Khlebnikov
2019-05-28 7:38 ` Michal Hocko
2019-05-28 8:04 ` Konstantin Khlebnikov
2019-05-28 8:42 ` Michal Hocko
2019-05-28 8:58 ` Konstantin Khlebnikov
2019-05-28 14:56 ` Shakeel Butt
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=e17e1370-9e88-e50c-94e3-736c122c1baf@yandex-team.ru \
--to=khlebnikov@yandex-team.ru \
--cc=akpm@linux-foundation.org \
--cc=guro@fb.com \
--cc=hannes@cmpxchg.org \
--cc=linux-api@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=mgorman@techsingularity.net \
--cc=mhocko@kernel.org \
--cc=tj@kernel.org \
--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