From: Ryan Roberts <ryan.roberts@arm.com>
To: John Hubbard <jhubbard@nvidia.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: LKML <linux-kernel@vger.kernel.org>,
linux-mm@kvack.org, David Hildenbrand <david@redhat.com>
Subject: Re: [PATCH] mm/memory.c: do_numa_page(): remove a redundant page table read
Date: Thu, 29 Feb 2024 11:35:18 +0000 [thread overview]
Message-ID: <ce00f9b2-f73f-4ae8-864e-ef2b9a62dbf5@arm.com> (raw)
In-Reply-To: <20240228034151.459370-1-jhubbard@nvidia.com>
On 28/02/2024 03:41, John Hubbard wrote:
> do_numa_page() is reading from the same page table entry, twice, while
> holding the page table lock: once while checking that the pte hasn't
> changed, and again in order to modify the pte.
>
> Instead, just read the pte once, and save it in the same old_pte
> variable that already exists. This has no effect on behavior, other than
> to provide a tiny potential improvement to performance, by avoiding the
> redundant memory read (which the compiler cannot elide, due to
> READ_ONCE()).
>
> Also improve the associated comments nearby.
>
> Cc: Ryan Roberts <ryan.roberts@arm.com>
> Cc: David Hildenbrand <david@redhat.com>
> Signed-off-by: John Hubbard <jhubbard@nvidia.com>
Reviewed-by: Ryan Roberts <ryan.roberts@arm.com>
> ---
> mm/memory.c | 12 ++++++------
> 1 file changed, 6 insertions(+), 6 deletions(-)
>
> diff --git a/mm/memory.c b/mm/memory.c
> index 0bfc8b007c01..df0711982901 100644
> --- a/mm/memory.c
> +++ b/mm/memory.c
> @@ -4928,18 +4928,18 @@ static vm_fault_t do_numa_page(struct vm_fault *vmf)
> int flags = 0;
>
> /*
> - * The "pte" at this point cannot be used safely without
> - * validation through pte_unmap_same(). It's of NUMA type but
> - * the pfn may be screwed if the read is non atomic.
> + * The pte cannot be used safely until we verify, while holding the page
> + * table lock, that its contents have not changed during fault handling.
> */
> spin_lock(vmf->ptl);
> - if (unlikely(!pte_same(ptep_get(vmf->pte), vmf->orig_pte))) {
> + /* Read the live PTE from the page tables: */
> + old_pte = ptep_get(vmf->pte);
> +
> + if (unlikely(!pte_same(old_pte, vmf->orig_pte))) {
> pte_unmap_unlock(vmf->pte, vmf->ptl);
> goto out;
> }
>
> - /* Get the normal PTE */
> - old_pte = ptep_get(vmf->pte);
> pte = pte_modify(old_pte, vma->vm_page_prot);
>
> /*
prev parent reply other threads:[~2024-02-29 11:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-28 3:41 John Hubbard
2024-02-28 9:11 ` David Hildenbrand
2024-02-29 11:35 ` Ryan Roberts [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=ce00f9b2-f73f-4ae8-864e-ef2b9a62dbf5@arm.com \
--to=ryan.roberts@arm.com \
--cc=akpm@linux-foundation.org \
--cc=david@redhat.com \
--cc=jhubbard@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
/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