linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: yang.yang29@zte.com.cn, akpm@linux-foundation.org
Cc: imbrenda@linux.ibm.com, linux-kernel@vger.kernel.org,
	linux-mm@kvack.org, ran.xiaokai@zte.com.cn, xu.xin.sc@gmail.com,
	xu.xin16@zte.com.cn, jiang.xuexin@zte.com.cn
Subject: Re: [PATCH v9 0/5] ksm: support tracking KSM-placed zero-pages
Date: Wed, 24 May 2023 11:12:28 +0200	[thread overview]
Message-ID: <dbc686ac-2d28-8cd8-417b-4d10477d0f79@redhat.com> (raw)
In-Reply-To: <202305241351365661923@zte.com.cn>

On 24.05.23 07:51, yang.yang29@zte.com.cn wrote:
> From: xu xin <xu.xin16@zte.com.cn>
> 
> 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. But the problem is, when
> enabling use_zero_pages, all empty pages will be merged with kernel zero
> pages instead of with each other as use_zero_pages is disabled, and then
> these zero-pages are no longer monitored by KSM.
> 
> The motivations to do this is seen at:
> https://lore.kernel.org/lkml/202302100915227721315@zte.com.cn/
> 
> In one word, we hope to implement the support for KSM-placed zero pages
> tracking without affecting the feature of use_zero_pages, so that app
> developer can also benefit from knowing the actual KSM profit by getting
> KSM-placed zero pages to optimize applications eventually when
> /sys/kernel/mm/ksm/use_zero_pages is enabled.
> 


Ran the tests and they worked as expected. I only had some remaining 
feedback for the last patch, otherwise LGTM.

-- 
Thanks,

David / dhildenb



  parent reply	other threads:[~2023-05-24  9:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24  5:51 yang.yang29
     [not found] ` <20230524055711.20387-1-yang.yang29@zte.com.cn>
2023-05-24  7:10   ` [PATCH v9 1/5] ksm: support unsharing KSM-placed zero pages David Hildenbrand
     [not found] ` <20230524055752.20449-1-yang.yang29@zte.com.cn>
2023-05-24  7:23   ` [PATCH v9 2/5] ksm: count all zero pages placed by KSM David Hildenbrand
2023-05-24  7:55     ` xu xin
2023-05-24  8:27       ` David Hildenbrand
     [not found] ` <20230524055851.20565-1-yang.yang29@zte.com.cn>
2023-05-24  7:25   ` [PATCH v9 4/5] ksm: consider KSM-placed zeropages when calculating KSM profit David Hildenbrand
     [not found] ` <20230524055906.20614-1-yang.yang29@zte.com.cn>
2023-05-24  9:11   ` [PATCH v9 5/5] selftest: add a testcase of ksm zero pages David Hildenbrand
2023-05-24  9:38     ` xu xin
2023-05-24  9:12 ` David Hildenbrand [this message]
     [not found] ` <20230524055800.20498-1-yang.yang29@zte.com.cn>
2023-05-24  7:24   ` [PATCH v9 3/5] ksm: add ksm zero pages for each process David Hildenbrand
2023-05-25  3:36   ` kernel test robot
2023-05-25  6:56   ` kernel test robot
2023-05-29  1:48     ` 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=dbc686ac-2d28-8cd8-417b-4d10477d0f79@redhat.com \
    --to=david@redhat.com \
    --cc=akpm@linux-foundation.org \
    --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