From: zhangqilong <zhangqilong3@huawei.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
Cc: "akpm@linux-foundation.org" <akpm@linux-foundation.org>,
"david@redhat.com" <david@redhat.com>,
"Liam.Howlett@oracle.com" <Liam.Howlett@oracle.com>,
"vbabka@suse.cz" <vbabka@suse.cz>,
"rppt@kernel.org" <rppt@kernel.org>,
"surenb@google.com" <surenb@google.com>,
"mhocko@suse.com" <mhocko@suse.com>,
"jannh@google.com" <jannh@google.com>,
"pfalcato@suse.de" <pfalcato@suse.de>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Wangkefeng (OS Kernel Lab)" <wangkefeng.wang@huawei.com>,
Sunnanyong <sunnanyong@huawei.com>
Subject: Re: [RFC PATCH 3/3] mm/mremap: Use can_pte_batch_count() instead of folio_pte_batch() for pte batch
Date: Tue, 28 Oct 2025 13:27:09 +0000 [thread overview]
Message-ID: <8dc1d253056848dba950e74bed8218bd@huawei.com> (raw)
> On Mon, Oct 27, 2025 at 10:03:15PM +0800, Zhang Qilong wrote:
> > In current mremap_folio_pte_batch(), 1) pte_batch_hint() always return
> > one pte in non-ARM64 machine, it is not efficient. 2) Next,
>
> Err... but there's basically no benefit for non-arm64 machines?
It except have benefit in non-arm64 machines. In non-arm64 machine,
pte_batch_hint always return one although a folio are mapped by multiple
PTEs.
>
> The key benefit is the mTHP side of things and making the underlying arch-
> specific code more efficient right?
Yes, we except it could benefit from mTHP, and not just for arm64.
>
> And again you need to get numbers to demonstrate you don't regress non-
> arm64.
Yes, I will have a test on x86-64, non-contiguous folios or non-contiguous-folio
should not cause regression. Thanks for your kind reminder.
>
> > it need to acquire a folio to call the folio_pte_batch().
> >
> > Due to new added can_pte_batch_count(), we just call it instead of
> > folio_pte_batch(). And then rename mremap_folio_pte_batch() to
> > mremap_pte_batch().
> >
> > Signed-off-by: Zhang Qilong <zhangqilong3@huawei.com>
> > ---
> > mm/mremap.c | 16 +++-------------
> > 1 file changed, 3 insertions(+), 13 deletions(-)
> >
> > diff --git a/mm/mremap.c b/mm/mremap.c index
> > bd7314898ec5..d11f93f1622f 100644
> > --- a/mm/mremap.c
> > +++ b/mm/mremap.c
> > @@ -169,27 +169,17 @@ static pte_t move_soft_dirty_pte(pte_t pte)
> > pte = pte_swp_mksoft_dirty(pte);
> > #endif
> > return pte;
> > }
> >
> > -static int mremap_folio_pte_batch(struct vm_area_struct *vma,
> > unsigned long addr,
> > +static int mremap_pte_batch(struct vm_area_struct *vma, unsigned long
> > +addr,
> > pte_t *ptep, pte_t pte, int max_nr) {
> > - struct folio *folio;
> > -
> > if (max_nr == 1)
> > return 1;
> >
> > - /* Avoid expensive folio lookup if we stand no chance of benefit. */
> > - if (pte_batch_hint(ptep, pte) == 1)
> > - return 1;
>
> Why are we eliminating an easy exit here and instead always invoking the more
> involved function?
>
> Again this has to be tested against non-arm architectures.
>
> > -
> > - folio = vm_normal_folio(vma, addr, pte);
> > - if (!folio || !folio_test_large(folio))
> > - return 1;
> > -
> > - return folio_pte_batch(folio, ptep, pte, max_nr);
> > + return can_pte_batch_count(vma, ptep, &pte, max_nr, 0);
>
> This is very silly to have this function now ust return another function + a trivial
> check that your function should be doing...
>
> > }
> >
> > static int move_ptes(struct pagetable_move_control *pmc,
> > unsigned long extent, pmd_t *old_pmd, pmd_t *new_pmd)
> { @@ -278,11
> > +268,11 @@ static int move_ptes(struct pagetable_move_control *pmc,
> > * make sure the physical page stays valid until
> > * the TLB entry for the old mapping has been
> > * flushed.
> > */
> > if (pte_present(old_pte)) {
> > - nr_ptes = mremap_folio_pte_batch(vma, old_addr,
> old_ptep,
> > + nr_ptes = mremap_pte_batch(vma, old_addr, old_ptep,
> > old_pte,
> max_nr_ptes);
> > force_flush = true;
> > }
> > pte = get_and_clear_ptes(mm, old_addr, old_ptep, nr_ptes);
> > pte = move_pte(pte, old_addr, new_addr);
> > --
> > 2.43.0
> >
next reply other threads:[~2025-10-28 13:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-28 13:27 zhangqilong [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-10-28 13:01 zhangqilong
2025-10-27 14:03 [RFC PATCH 0/3] mm: PTEs batch optimization in mincore and mremap Zhang Qilong
2025-10-27 14:03 ` [RFC PATCH 3/3] mm/mremap: Use can_pte_batch_count() instead of folio_pte_batch() for pte batch Zhang Qilong
2025-10-27 19:41 ` David Hildenbrand
2025-10-27 19:57 ` Lorenzo Stoakes
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=8dc1d253056848dba950e74bed8218bd@huawei.com \
--to=zhangqilong3@huawei.com \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=jannh@google.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mhocko@suse.com \
--cc=pfalcato@suse.de \
--cc=rppt@kernel.org \
--cc=sunnanyong@huawei.com \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--cc=wangkefeng.wang@huawei.com \
/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