From: Andrew Morton <akpm@linux-foundation.org>
To: xu xin <xu.xin.sc@gmail.com>
Cc: david@redhat.com, imbrenda@linux.ibm.com,
jiang.xuexin@zte.com.cn, linux-kernel@vger.kernel.org,
linux-mm@kvack.org, ran.xiaokai@zte.com.cn, xu.xin16@zte.com.cn,
yang.yang29@zte.com.cn
Subject: Re: [PATCH v3 0/5] ksm: support tracking KSM-placed zero-pages
Date: Tue, 18 Oct 2022 15:54:07 -0700 [thread overview]
Message-ID: <20221018155407.41c993924ec09a64ae966d50@linux-foundation.org> (raw)
In-Reply-To: <20221018090022.373574-1-xu.xin16@zte.com.cn>
On Tue, 18 Oct 2022 09:00:22 +0000 xu xin <xu.xin.sc@gmail.com> wrote:
> >A full description of the real-world end-user operational benefits of
> >these changes would help, please.
> >
>
> The core idea of this patch set is to enable users to perceive the number of any
> pages merged by KSM, regardless of whether use_zero_page switch has been turned
> on, so that users can know how much free memory increase is really due to their
> madvise(MERGEABLE) actions.
OK, thanks.
> The motivation for me to do this is that when I do
> an application optimization of KSM on embedded Linux for 5G platform, I find
> that ksm_merging_pages of some process becomes very small(but used to be large),
> which led me to think that there was any problem with the application KSM-madvise
> strategy, but in fact, it was only because use_zero_pages is on.
Please expand on the above motivation and experience, and include it in
the [0/n] changelog. But let's leave it a few days to see if there's
additional reviewer input.
next prev parent reply other threads:[~2022-10-18 22:54 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-11 2:20 xu.xin.sc
2022-10-11 2:21 ` [PATCH v3 1/5] ksm: abstract the function try_to_get_old_rmap_item xu.xin.sc
2022-10-11 2:22 ` [PATCH v3 2/5] ksm: support unsharing zero pages placed by KSM xu.xin.sc
2022-10-21 10:17 ` David Hildenbrand
2022-10-21 12:54 ` David Hildenbrand
2022-11-09 10:40 ` David Hildenbrand
2022-11-14 3:02 ` xu xin
2022-10-11 2:22 ` [PATCH v3 3/5] ksm: count all " xu.xin.sc
2022-10-11 2:22 ` [PATCH v3 4/5] ksm: count zero pages for each process xu.xin.sc
2022-10-11 2:23 ` [PATCH v3 5/5] ksm: add zero_pages_sharing documentation xu.xin.sc
2022-10-17 23:55 ` [PATCH v3 0/5] ksm: support tracking KSM-placed zero-pages Andrew Morton
2022-10-18 9:00 ` xu xin
2022-10-18 22:54 ` Andrew Morton [this message]
2022-10-21 10:18 ` [PATCH " David Hildenbrand
2022-10-24 3:07 ` xu xin
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=20221018155407.41c993924ec09a64ae966d50@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=imbrenda@linux.ibm.com \
--cc=jiang.xuexin@zte.com.cn \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ran.xiaokai@zte.com.cn \
--cc=xu.xin.sc@gmail.com \
--cc=xu.xin16@zte.com.cn \
--cc=yang.yang29@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