[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <YoSZE7Iak3AYA4VE@balbir-desktop>
Date: Wed, 18 May 2022 16:58:27 +1000
From: Balbir Singh <bsingharora@...il.com>
To: cgel.zte@...il.com
Cc: akpm@...ux-foundation.org, ammarfaizi2@...weeb.org,
oleksandr@...alenko.name, willy@...radead.org, linux-mm@...ck.org,
corbet@....net, linux-kernel@...r.kernel.org,
xu xin <xu.xin16@....com.cn>,
Yang Yang <yang.yang29@....com.cn>,
Ran Xiaokai <ran.xiaokai@....com.cn>,
wangyong <wang.yong12@....com.cn>,
Yunkai Zhang <zhang.yunkai@....com.cn>,
Jiang Xuexin <jiang.xuexin@....com.cn>
Subject: Re: [PATCH] mm/ksm: introduce ksm_enabled for each process
On Tue, May 17, 2022 at 09:27:01AM +0000, cgel.zte@...il.com wrote:
> From: xu xin <xu.xin16@....com.cn>
>
> For now, if we want to use KSM to merge pages of some apps, we have to
> explicitly call madvise() in application code, which means installed
> apps on OS needs to be uninstall and source code needs to be modified.
> It is very inconvenient because sometimes users or app developers are not
> willing to modify their app source codes for any reasons.
>
I thought we got process_madvise in 5.13, doesn't that help solve the
problem with extensions to advice and an appropriate wrapper? Granted
it might be a little racy with a running process potentially
participating in KSM already. If we are concerned about KSM, I would
assume that we care about long running processes, is that true?
Balbir Singh
Powered by blists - more mailing lists