From: David Hildenbrand <david@redhat.com>
To: 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 v5 1/6] ksm: abstract the function try_to_get_old_rmap_item
Date: Wed, 18 Jan 2023 15:03:38 +0100 [thread overview]
Message-ID: <0e0c90a2-d12c-f965-9cce-ecd5d28c09dd@redhat.com> (raw)
In-Reply-To: <202212300912449061763@zte.com.cn>
On 30.12.22 02:12, yang.yang29@zte.com.cn wrote:
> From: xu xin <xu.xin16@zte.com.cn>
>
> A new function try_to_get_old_rmap_item is abstracted from
> get_next_rmap_item. This function will be reused by the subsequent
> patches about counting ksm_zero_pages.
>
> The patch improves the readability and reusability of KSM code.
>
> Signed-off-by: xu xin <xu.xin16@zte.com.cn>
> Cc: David Hildenbrand <david@redhat.com>
> Cc: Claudio Imbrenda <imbrenda@linux.ibm.com>
> Cc: Xuexin Jiang <jiang.xuexin@zte.com.cn>
> Reviewed-by: Xiaokai Ran <ran.xiaokai@zte.com.cn>
> Reviewed-by: Yang Yang <yang.yang29@zte.com.cn>
> ---
> mm/ksm.c | 25 +++++++++++++++++++------
> 1 file changed, 19 insertions(+), 6 deletions(-)
>
> diff --git a/mm/ksm.c b/mm/ksm.c
> index 83e2f74ae7da..5b0a7343ff4a 100644
> --- a/mm/ksm.c
> +++ b/mm/ksm.c
> @@ -2214,23 +2214,36 @@ static void cmp_and_merge_page(struct page *page, struct ksm_rmap_item *rmap_ite
> }
> }
>
> -static struct ksm_rmap_item *get_next_rmap_item(struct ksm_mm_slot *mm_slot,
> - struct ksm_rmap_item **rmap_list,
> - unsigned long addr)
> +static struct ksm_rmap_item *try_to_get_old_rmap_item(unsigned long addr,
> + struct ksm_rmap_item **rmap_list)
> {
> - struct ksm_rmap_item *rmap_item;
> -
> while (*rmap_list) {
> - rmap_item = *rmap_list;
> + struct ksm_rmap_item *rmap_item = *rmap_list;
Empty line missing.
> if ((rmap_item->address & PAGE_MASK) == addr)
> return rmap_item;
> if (rmap_item->address > addr)
> break;
> *rmap_list = rmap_item->rmap_list;
> + /* Running here indicates it's vma has been UNMERGEABLE */
"If we end up here, the VMA is UNMERGEABLE."
Although I am not sure if that is true?
> remove_rmap_item_from_tree(rmap_item);
> free_rmap_item(rmap_item);
> }
>
> + return NULL;
> +}
> +
> +static struct ksm_rmap_item *get_next_rmap_item(struct ksm_mm_slot *mm_slot,
> + struct ksm_rmap_item **rmap_list,
> + unsigned long addr)
> +{
> + struct ksm_rmap_item *rmap_item;
> +
> + /* lookup if we have a old rmap_item matching the addr*/
I suggest dropping that comment, "try_to_get_old_rmap_item()" is
expressive enough.
> + rmap_item = try_to_get_old_rmap_item(addr, rmap_list);
> + if (rmap_item)
> + return rmap_item;
> +
> + /* Need to allocate a new rmap_item */
I suggest dropping that comment for the same reason.
> rmap_item = alloc_rmap_item();
> if (rmap_item) {
> /* It has already been zeroed */
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2023-01-18 14:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-30 1:12 yang.yang29
2023-01-18 14:03 ` David Hildenbrand [this message]
2023-02-04 6:43 ` yang.yang29
2023-02-13 12:51 ` 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=0e0c90a2-d12c-f965-9cce-ecd5d28c09dd@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