From: David Hildenbrand <david@redhat.com>
To: Nadav Amit <nadav.amit@gmail.com>, linux-mm@kvack.org
Cc: Andrew Morton <akpm@linux-foundation.org>,
Nadav Amit <namit@vmware.com>,
Mike Kravetz <mike.kravetz@oracle.com>,
Hugh Dickins <hughd@google.com>,
Axel Rasmussen <axelrasmussen@google.com>,
Mike Rapoport <rppt@linux.ibm.com>, Peter Xu <peterx@redhat.com>
Subject: Re: [PATCH v2 4/5] userfaultfd: zero access/write hints
Date: Fri, 22 Jul 2022 09:47:55 +0200 [thread overview]
Message-ID: <f51ea0f8-5d2f-3b33-4a30-928b3038595a@redhat.com> (raw)
In-Reply-To: <20220718114748.2623-5-namit@vmware.com>
On 18.07.22 13:47, Nadav Amit wrote:
> From: Nadav Amit <namit@vmware.com>
>
> When userfaultfd provides a zeropage in response to ioctl, it provides a
> readonly alias to the zero page. If the page is later written (which is
> the likely scenario), page-fault occurs and the page-fault allocator
> allocates a page and rewires the page-tables.
>
> This is an expensive flow for cases in which a page is likely be written
> to. Users can use the copy ioctl to initialize zero page (by copying
> zeros), but this is also wasteful.
>
> Allow userfaultfd users to efficiently map initialized zero-pages that
> are writable. IF UFFDIO_ZEROPAGE_MODE_WRITE_LIKELY is provided would map
> a clear page instead of an alias to the zero page.
>
> Suggested-by: David Hildenbrand <david@redhat.com>
> Cc: Mike Kravetz <mike.kravetz@oracle.com>
> Cc: Hugh Dickins <hughd@google.com>
> Cc: Andrew Morton <akpm@linux-foundation.org>
> Cc: Axel Rasmussen <axelrasmussen@google.com>
> Cc: Mike Rapoport <rppt@linux.ibm.com>
> Acked-by: Peter Xu <peterx@redhat.com>
> Signed-off-by: Nadav Amit <namit@vmware.com>
> ---
> mm/userfaultfd.c | 35 +++++++++++++++++++++++++++++++++++
> 1 file changed, 35 insertions(+)
>
> diff --git a/mm/userfaultfd.c b/mm/userfaultfd.c
> index c15679f3eb6a..954c6980b29f 100644
> --- a/mm/userfaultfd.c
> +++ b/mm/userfaultfd.c
> @@ -241,6 +241,37 @@ static int mfill_zeropage_pte(struct mm_struct *dst_mm,
> return ret;
> }
>
> +static int mfill_clearpage_pte(struct mm_struct *dst_mm, pmd_t *dst_pmd,
> + struct vm_area_struct *dst_vma,
> + unsigned long dst_addr,
> + uffd_flags_t uffd_flags)
> +{
> + struct page *page;
> + int ret;
> +
> + ret = -ENOMEM;
> + page = alloc_zeroed_user_highpage_movable(dst_vma, dst_addr);
> + if (!page)
> + goto out;
> +
> + /* The PTE is not marked as dirty unconditionally */
> + SetPageDirty(page);
> + __SetPageUptodate(page);
> +
> + if (mem_cgroup_charge(page_folio(page), dst_vma->vm_mm, GFP_KERNEL))
> + goto out_release;
> +
> + ret = mfill_atomic_install_pte(dst_mm, dst_pmd, dst_vma, dst_addr,
> + page, true, uffd_flags);
> + if (ret)
> + goto out_release;
> +out:
> + return ret;
> +out_release:
> + put_page(page);
> + goto out;
> +}
> +
> /* Handles UFFDIO_CONTINUE for all shmem VMAs (shared or private). */
> static int mcontinue_atomic_pte(struct mm_struct *dst_mm,
> pmd_t *dst_pmd,
> @@ -500,6 +531,10 @@ static __always_inline ssize_t mfill_atomic_pte(struct mm_struct *dst_mm,
> err = mcopy_atomic_pte(dst_mm, dst_pmd, dst_vma,
> dst_addr, src_addr, page,
> uffd_flags);
> + else if (!(uffd_flags & UFFD_FLAGS_WP) &&
> + (uffd_flags & UFFD_FLAGS_WRITE_LIKELY))
> + err = mfill_clearpage_pte(dst_mm, dst_pmd, dst_vma,
> + dst_addr, uffd_flags);
> else
> err = mfill_zeropage_pte(dst_mm, dst_pmd,
> dst_vma, dst_addr, uffd_flags);
Reviewed-by: David Hildenbrand <david@redhat.com>
--
Thanks,
David / dhildenb
next prev parent reply other threads:[~2022-07-22 7:48 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 11:47 [PATCH v2 0/5] userfaultfd: support " Nadav Amit
2022-07-18 11:47 ` [PATCH v2 2/5] userfaultfd: introduce access-likely mode for common operations Nadav Amit
2022-07-18 20:05 ` Peter Xu
2022-07-18 20:59 ` Nadav Amit
2022-07-18 21:21 ` Peter Xu
2022-07-23 9:16 ` Mike Rapoport
2022-07-25 17:18 ` Nadav Amit
2022-07-26 16:02 ` Mike Rapoport
2022-07-18 11:47 ` [PATCH v2 3/5] userfaultfd: introduce write-likely mode for uffd operations Nadav Amit
2022-07-18 20:12 ` Peter Xu
2022-07-18 20:25 ` Nadav Amit
2022-07-18 21:27 ` Peter Xu
2022-07-18 11:47 ` [PATCH v2 4/5] userfaultfd: zero access/write hints Nadav Amit
2022-07-22 7:47 ` David Hildenbrand [this message]
2022-07-18 11:47 ` [PATCH v2 5/5] selftest/userfaultfd: test read/write hints Nadav Amit
[not found] ` <20220718114748.2623-2-namit@vmware.com>
2022-07-18 20:05 ` [PATCH v2 1/5] userfaultfd: introduce uffd_flags Peter Xu
2022-07-22 7:54 ` David Hildenbrand
2022-07-22 18:47 ` Nadav Amit
2022-07-23 9:12 ` Mike Rapoport
2022-07-25 17:23 ` Nadav Amit
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=f51ea0f8-5d2f-3b33-4a30-928b3038595a@redhat.com \
--to=david@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=hughd@google.com \
--cc=linux-mm@kvack.org \
--cc=mike.kravetz@oracle.com \
--cc=nadav.amit@gmail.com \
--cc=namit@vmware.com \
--cc=peterx@redhat.com \
--cc=rppt@linux.ibm.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