[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190516104412.GN16651@dhcp22.suse.cz>
Date: Thu, 16 May 2019 12:44:12 +0200
From: Michal Hocko <mhocko@...nel.org>
To: Oleksandr Natalenko <oleksandr@...hat.com>
Cc: linux-kernel@...r.kernel.org, Kirill Tkhai <ktkhai@...tuozzo.com>,
Hugh Dickins <hughd@...gle.com>,
Alexey Dobriyan <adobriyan@...il.com>,
Vlastimil Babka <vbabka@...e.cz>,
Matthew Wilcox <willy@...radead.org>,
Pavel Tatashin <pasha.tatashin@...een.com>,
Greg KH <greg@...ah.com>,
Suren Baghdasaryan <surenb@...gle.com>,
Minchan Kim <minchan@...nel.org>,
Timofey Titovets <nefelim4ag@...il.com>,
Aaron Tomlin <atomlin@...hat.com>,
Grzegorz Halat <ghalat@...hat.com>, linux-mm@...ck.org,
linux-api@...r.kernel.org
Subject: Re: [PATCH RFC 0/5] mm/ksm, proc: introduce remote madvise
On Thu 16-05-19 11:42:29, Oleksandr Natalenko wrote:
[...]
> * to mark all the eligible VMAs as mergeable, use:
>
> # echo merge > /proc/<pid>/madvise
>
> * to unmerge all the VMAs, use:
>
> # echo unmerge > /proc/<pid>/madvise
Please do not open a new thread until a previous one reaches some
conclusion. I have outlined some ways to go forward in
http://lkml.kernel.org/r/20190515145151.GG16651@dhcp22.suse.cz.
I haven't heard any feedback on that, yet you open a 3rd way in a
different thread. This will not help to move on with the discussion.
Please follow up on that thread.
--
Michal Hocko
SUSE Labs
Powered by blists - more mailing lists