linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: xu xin <xu.xin.sc@gmail.com>
To: david@redhat.com
Cc: akpm@linux-foundation.org, 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, yang.yang29@zte.com.cn
Subject: Re: [PATCH v9 2/5] ksm: count all zero pages placed by KSM
Date: Wed, 24 May 2023 15:55:39 +0800	[thread overview]
Message-ID: <20230524075539.20844-1-xu.xin16@zte.com.cn> (raw)
In-Reply-To: <52bfd744-3086-a22a-e2e7-8b64d5fccfcc@redhat.com>

>> +extern unsigned long ksm_zero_pages;
>> +
>> +static inline void ksm_notify_unmap_zero_page(pte_t pte)
>> +{
>> +	if (is_ksm_zero_pte(pte))
>> +		ksm_zero_pages--;
>> +}
>> +
>>   static inline int ksm_fork(struct mm_struct *mm, struct mm_struct *oldmm)
>>   {
>>   	int ret;
>> @@ -103,6 +111,10 @@ static inline void ksm_exit(struct mm_struct *mm)
>>   
>>   #define is_ksm_zero_pte(pte)	0
>>   
>> +static inline void ksm_notify_unmap_zero_page(pte_t pte)
>> +{
>> +}
>> +
>
>Having proposed that name ... I realize that we call this function 
>whenever there might be a zeropage mapped (when we have !page after 
>vm_normal_page()) -- but it could also not be the zeropage.
>
>Not really able to come up with a better name :)
>
>ksm_notify_maybe_unmap_zero_page ?
>
>ksm_maybe_unmap_zero_page ?
>

Analogous to the existing name of ksm_might_need_to_copy, so maybe we can use
'ksm_might_unmap_zero_page', 

>
>Maybe someone else reading along has a better idea. In any case, the 
>logic itself LGTM



  reply	other threads:[~2023-05-24  7:55 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 [this message]
2023-05-24  8:27       ` David Hildenbrand
     [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
     [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

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=20230524075539.20844-1-xu.xin16@zte.com.cn \
    --to=xu.xin.sc@gmail.com \
    --cc=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.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