From: Michal Hocko <mhocko@suse.com>
To: CGEL <cgel.zte@gmail.com>
Cc: Balbir Singh <bsingharora@gmail.com>,
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 processg
Date: Wed, 18 May 2022 14:14:28 +0200 [thread overview]
Message-ID: <YoTjJH7+QD+DSrW8@dhcp22.suse.cz> (raw)
In-Reply-To: <6284a2ef.1c69fb81.e53cd.32b2@mx.google.com>
On Wed 18-05-22 07:40:30, CGEL wrote:
[...]
> 2. process_madvise is still a kind of madvise. processs_madvise from
> another process overrides the intention of origin app code ifself that
> also calls madvise, which is unrecoverable. For example, if a process "A"
> which madvises just one part of VMAs (not all) as MERGEABLE run on the OS
> already, meanwhile, if another process which doesn't know the information
> of "A" 's MERGEABLE areas, then call process_madvise to advise all VMAs of
> "A" as MERGEABLE, the original MERGEABLE information of "A" calling madivse
> is erasured permanently.
I do not really follow. How is this any different from an external
process modifying the process wide policy via the proc or any other
interface?
--
Michal Hocko
SUSE Labs
next prev parent reply other threads:[~2022-05-18 12:14 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
2022-05-18 7:40 ` [PATCH] mm/ksm: introduce ksm_enabled for each processg CGEL
2022-05-18 12:14 ` Michal Hocko [this message]
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=YoTjJH7+QD+DSrW8@dhcp22.suse.cz \
--to=mhocko@suse.com \
--cc=akpm@linux-foundation.org \
--cc=ammarfaizi2@gnuweeb.org \
--cc=bsingharora@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).