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,
wang.yong12@zte.com.cn
Subject: Re: [PATCH] ksm: delay the check of splitting compound pages
Date: Tue, 14 Nov 2023 14:02:22 +0100 [thread overview]
Message-ID: <938be193-8a73-432e-b424-53afa9f8c38e@redhat.com> (raw)
In-Reply-To: <202311142036302357580@zte.com.cn>
On 14.11.23 13:36, yang.yang29@zte.com.cn wrote:
> From: xu xin <xu.xin16@zte.com.cn>
>
> Background
> ==========
> When trying to merge two pages, it may fail because the two pages
> belongs to the same compound page and split_huge_page fails due to
> the incorrect reference to the page. To solve the problem, the commit
> 77da2ba0648a4 ("mm/ksm: fix interaction with THP") tries to split the
> compound page after try_to_merge_two_pages() fails and put_page in
> that case. However it is too early to calculate of the variable 'split' which
> indicates whether the two pages belongs to the same compound page.
>
> What to do
> ==========
> If try_to_merge_two_pages() succeeds, there is no need to check whether
> to splitting compound pages. So we delay the check of splitting compound
> pages until try_to_merge_two_pages() fails, which can improve the
> processing efficiency of cmp_and_merge_page() a little.
>
> Signed-off-by: xu xin <xu.xin16@zte.com.cn>
> Reviewed-by: Yang Yang <yang.yang29@zte.com.cn>
Can we please add a unit test to ksm_functional_tests.c so we actually
get it right this time?
--
Cheers,
David / dhildenb
next prev parent reply other threads:[~2023-11-14 13:02 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-14 12:36 yang.yang29
2023-11-14 13:02 ` David Hildenbrand [this message]
2023-11-15 3:15 ` xu
2023-11-15 10:52 ` David Hildenbrand
2023-11-14 14:43 ` David Hildenbrand
2023-11-15 3:11 ` xu
2023-11-15 10:49 ` David Hildenbrand
2023-11-16 12:17 ` xu
2023-11-16 17:39 ` David Hildenbrand
2023-11-16 18:06 ` 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=938be193-8a73-432e-b424-53afa9f8c38e@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=wang.yong12@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