From: Balbir Singh <bsingharora@gmail.com>
To: cgel.zte@gmail.com
Cc: akpm@linux-foundation.org, ammarfaizi2@gnuweeb.org,
oleksandr@natalenko.name, willy@infradead.org,
linux-mm@kvack.org, corbet@lwn.net, linux-kernel@vger.kernel.org,
xu xin <xu.xin16@zte.com.cn>, Yang Yang <yang.yang29@zte.com.cn>,
Ran Xiaokai <ran.xiaokai@zte.com.cn>,
wangyong <wang.yong12@zte.com.cn>,
Yunkai Zhang <zhang.yunkai@zte.com.cn>,
Jiang Xuexin <jiang.xuexin@zte.com.cn>
Subject: Re: [PATCH] mm/ksm: introduce ksm_enabled for each process
Date: Wed, 18 May 2022 16:58:27 +1000 [thread overview]
Message-ID: <YoSZE7Iak3AYA4VE@balbir-desktop> (raw)
In-Reply-To: <20220517092701.1662641-1-xu.xin16@zte.com.cn>
On Tue, May 17, 2022 at 09:27:01AM +0000, cgel.zte@gmail.com wrote:
> From: xu xin <xu.xin16@zte.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
next prev parent reply other threads:[~2022-05-18 6:58 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-17 9:27 [PATCH] mm/ksm: introduce ksm_enabled for each process cgel.zte
2022-05-17 14:04 ` Michal Hocko
2022-05-18 2:47 ` CGEL
2022-05-18 12:12 ` Michal Hocko
2022-05-19 6:23 ` CGEL
2022-05-19 7:35 ` Michal Hocko
2022-05-19 8:02 ` CGEL
2022-05-19 8:24 ` Michal Hocko
2022-05-18 6:58 ` Balbir Singh [this message]
2022-05-18 7:40 ` [PATCH] mm/ksm: introduce ksm_enabled for each processg CGEL
2022-05-18 12:14 ` Michal Hocko
2022-05-19 6:35 ` CGEL
2022-05-19 7:39 ` Michal Hocko
2022-05-24 8:52 ` CGEL
2022-05-24 9:04 ` Michal Hocko
2022-05-25 6:56 ` CGEL
2022-05-25 7:38 ` Michal Hocko
2022-05-18 14:31 ` [PATCH] mm/ksm: introduce ksm_enabled for each process Jann Horn
2022-05-19 3:39 ` CGEL
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=YoSZE7Iak3AYA4VE@balbir-desktop \
--to=bsingharora@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=ammarfaizi2@gnuweeb.org \
--cc=cgel.zte@gmail.com \
--cc=corbet@lwn.net \
--cc=jiang.xuexin@zte.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=oleksandr@natalenko.name \
--cc=ran.xiaokai@zte.com.cn \
--cc=wang.yong12@zte.com.cn \
--cc=willy@infradead.org \
--cc=xu.xin16@zte.com.cn \
--cc=yang.yang29@zte.com.cn \
--cc=zhang.yunkai@zte.com.cn \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.