From: David Hildenbrand <david@redhat.com>
To: Baolin Wang <baolin.wang@linux.alibaba.com>, akpm@linux-foundation.org
Cc: 21cnbao@gmail.com, ryan.roberts@arm.com, dev.jain@arm.com,
ziy@nvidia.com, linux-mm@kvack.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3] mm: mincore: use pte_batch_bint() to batch process large folios
Date: Fri, 9 May 2025 14:42:28 +0200 [thread overview]
Message-ID: <c4dac352-5645-4037-a854-008d10a3a13c@redhat.com> (raw)
In-Reply-To: <3d52c5bb-60c5-4bfd-958e-737a8cc90853@linux.alibaba.com>
>
> I tried this method, and it had no impact on performance.
>
Might be that the compiler already did that for us.
--
Cheers,
David / dhildenb
prev parent reply other threads:[~2025-05-09 12:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-09 0:45 Baolin Wang
2025-05-09 1:49 ` Barry Song
2025-05-09 7:30 ` Dev Jain
2025-05-09 7:38 ` Baolin Wang
2025-05-09 7:51 ` David Hildenbrand
2025-05-09 12:25 ` Baolin Wang
2025-05-09 12:42 ` David Hildenbrand [this message]
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=c4dac352-5645-4037-a854-008d10a3a13c@redhat.com \
--to=david@redhat.com \
--cc=21cnbao@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=baolin.wang@linux.alibaba.com \
--cc=dev.jain@arm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=ryan.roberts@arm.com \
--cc=ziy@nvidia.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