[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20210125131935.GI827@dhcp22.suse.cz>
Date: Mon, 25 Jan 2021 14:19:35 +0100
From: Michal Hocko <mhocko@...e.com>
To: Suren Baghdasaryan <surenb@...gle.com>
Cc: linux-man@...r.kernel.org, akpm@...ux-foundation.org,
jannh@...gle.com, keescook@...omium.org, jeffv@...gle.com,
minchan@...nel.org, shakeelb@...gle.com, rientjes@...gle.com,
edgararriaga@...gle.com, timmurray@...gle.com, linux-mm@...ck.org,
selinux@...r.kernel.org, linux-security-module@...r.kernel.org,
linux-api@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel-team@...roid.com
Subject: Re: [PATCH 1/1] process_madvise.2: Add process_madvise man page
On Wed 20-01-21 12:23:37, Suren Baghdasaryan wrote:
[...]
> MADV_COLD (since Linux 5.4.1)
> Deactivate a given range of pages by moving them from active to
> inactive LRU list. This is done to accelerate the reclaim of these
> pages. The advice might be ignored for some pages in the range when it
> is not applicable.
I do not think we want to talk about active/inactive LRU lists here.
Wouldn't it be sufficient to say
Deactive a given range of pages which will make them a more probable
reclaim target should there be a memory pressure. This is a
non-destructive operation.
Other than that, looks good to me from the content POV.
Thanks!
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists