public inbox for linux-mm@kvack.org
 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 v9 3/5] ksm: add ksm zero pages for each process
Date: Wed, 24 May 2023 09:24:51 +0200	[thread overview]
Message-ID: <a2e53f37-e76a-930d-3020-2ebc4b3986b2@redhat.com> (raw)
In-Reply-To: <20230524055800.20498-1-yang.yang29@zte.com.cn>

On 24.05.23 07:58, 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>
> ---

[...]

>   static inline int ksm_fork(struct mm_struct *mm, struct mm_struct *oldmm)
> diff --git a/include/linux/mm_types.h b/include/linux/mm_types.h
> index 306a3d1a0fa6..14f781509812 100644
> --- a/include/linux/mm_types.h
> +++ b/include/linux/mm_types.h
> @@ -777,7 +777,7 @@ struct mm_struct {
>   #ifdef CONFIG_KSM
>   		/*
>   		 * Represent how many pages of this process are involved in KSM
> -		 * merging.
> +		 * merging (not including ksm_zero_pages).
>   		 */
>   		unsigned long ksm_merging_pages;
>   		/*
> @@ -785,7 +785,12 @@ struct mm_struct {
>   		 * including merged and not merged.
>   		 */
>   		unsigned long ksm_rmap_items;
> -#endif
> +		/*
> +		 * Represent how many empty pages are merged with kernel zero
> +		 * pages when enabling KSM use_zero_pages.

"zero page" ? Only some archs have multiple ones, and it's rather an 
implementation detail.

> +		 */
> +		unsigned long ksm_zero_pages;
> +#endif /* CONFIG_KSM */
>   #ifdef CONFIG_LRU_GEN
>   		struct {

Reviewed-by: David Hildenbrand <david@redhat.com>

-- 
Thanks,

David / dhildenb



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

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-24  5:51 [PATCH v9 0/5] ksm: support tracking KSM-placed zero-pages 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 ` [PATCH v9 0/5] ksm: support tracking KSM-placed zero-pages David Hildenbrand
     [not found] ` <20230524055800.20498-1-yang.yang29@zte.com.cn>
2023-05-24  7:24   ` David Hildenbrand [this message]
2023-05-25  3:36   ` [PATCH v9 3/5] ksm: add ksm zero pages for each process 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=a2e53f37-e76a-930d-3020-2ebc4b3986b2@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