linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: David Hildenbrand <david@redhat.com>
To: Yang Yang <yang.yang29@zte.com.cn>, akpm@linux-foundation.org
Cc: imbrenda@linux.ibm.com, jiang.xuexin@zte.com.cn,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	ran.xiaokai@zte.com.cn, xu.xin.sc@gmail.com, xu.xin16@zte.com.cn
Subject: Re: [PATCH v8 3/6] ksm: add ksm zero pages for each process
Date: Tue, 23 May 2023 11:55:43 +0200	[thread overview]
Message-ID: <4a38e04a-df69-5c5d-5631-152b662db7a7@redhat.com> (raw)
In-Reply-To: <20230522105305.4126-1-yang.yang29@zte.com.cn>

On 22.05.23 12:53, Yang Yang wrote:
> From: xu xin <xu.xin16@zte.com.cn>
> 
> As the number of ksm zero pages is not included in ksm_merging_pages per
> process when enabling use_zero_pages, it's unclear of how many actual
> pages are merged by KSM. To let users accurately estimate their memory
> demands when unsharing KSM zero-pages, it's necessary to show KSM zero-
> pages per process. In addition, it help users to know the actual KSM
> profit because KSM-placed zero pages are also benefit from KSM.
> 
> since unsharing zero pages placed by KSM accurately is achieved, then
> tracking empty pages merging and unmerging is not a difficult thing any
> longer.
> 
> Since we already have /proc/<pid>/ksm_stat, just add the information of
> 'ksm_zero_pages' in it.
> 
> Signed-off-by: xu xin <xu.xin16@zte.com.cn>
> Cc: Claudio Imbrenda <imbrenda@linux.ibm.com>
> Cc: David Hildenbrand <david@redhat.com>
> Cc: Xuexin Jiang <jiang.xuexin@zte.com.cn>
> Cc: Xiaokai Ran <ran.xiaokai@zte.com.cn>
> Cc: Yang Yang <yang.yang29@zte.com.cn>
> ---


LGTM. [inlining inc_ksm_zero_pages() and avoiding explicit 
dec_ksm_zero_pages() as noted on patch #2 ]

-- 
Thanks,

David / dhildenb



  parent reply	other threads:[~2023-05-23  9:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-22 10:42 [PATCH v8 0/6] ksm: support tracking KSM-placed zero-pages yang.yang29
     [not found] ` <20230522104908.3999-1-yang.yang29@zte.com.cn>
2023-05-23  9:41   ` [PATCH v8 1/6] ksm: support unsharing KSM-placed zero pages David Hildenbrand
2023-05-23 13:55     ` xu xin
2023-05-23 13:57     ` xu xin
2023-05-23 14:00       ` David Hildenbrand
2023-05-23 14:11         ` xu xin
     [not found] ` <20230522105229.4066-1-yang.yang29@zte.com.cn>
2023-05-23  9:47   ` [PATCH v8 2/6] ksm: count all zero pages placed by KSM David Hildenbrand
2023-05-23  9:51   ` David Hildenbrand
     [not found] ` <20230522105305.4126-1-yang.yang29@zte.com.cn>
2023-05-23  9:55   ` David Hildenbrand [this message]
     [not found] ` <20230522105335.4176-1-yang.yang29@zte.com.cn>
2023-05-23  9:58   ` [PATCH v8 4/6] ksm: add documentation for ksm zero pages David Hildenbrand
     [not found] ` <20230522105402.4225-1-yang.yang29@zte.com.cn>
2023-05-23 10:01   ` [PATCH v8 5/6] ksm: update the calculation of KSM profit David Hildenbrand
     [not found] ` <20230522105433.4277-1-yang.yang29@zte.com.cn>
2023-05-23 10:15   ` [PATCH v8 6/6] selftest: add a testcase of ksm zero pages David Hildenbrand

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=4a38e04a-df69-5c5d-5631-152b662db7a7@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