From: Peter Xu <peterx@redhat.com>
To: Muhammad Usama Anjum <usama.anjum@collabora.com>
Cc: David Hildenbrand <david@redhat.com>,
linux-kernel@vger.kernel.org, linux-mm@kvack.org,
Axel Rasmussen <axelrasmussen@google.com>,
Mike Rapoport <rppt@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>,
Andrea Arcangeli <aarcange@redhat.com>,
Nadav Amit <nadav.amit@gmail.com>
Subject: Re: [PATCH] mm/uffd: UFFD_FEATURE_WP_ZEROPAGE
Date: Fri, 17 Feb 2023 18:10:10 -0500 [thread overview]
Message-ID: <Y/AJUi4o5hOKDkgy@x1n> (raw)
In-Reply-To: <427298c4-0da9-059f-02ff-c5147d317c87@collabora.com>
Hi, Muhammad,
On Fri, Feb 17, 2023 at 05:31:19PM +0500, Muhammad Usama Anjum wrote:
> I've just ran my single threaded selftest [1] over an over again to get
> some numbers.
>
> Without zeropage
> qemu has 6 cores: 26.0355
Did you count in the time of read prefault? Or did you not prefault at
all?
> With zeropage
> qemu has 6 cores: 39.203
>
> 33% worse performance with zero pages
>
> Definitely, there can be better benchmark application. Please let me know
> if I should write better benchmarks on my end.
>
> [1]
> https://lore.kernel.org/all/20230202112915.867409-7-usama.anjum@collabora.com
I'll have a closer look too next week.
Thanks,
--
Peter Xu
next prev parent reply other threads:[~2023-02-17 23:10 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-15 21:02 [PATCH] mm/uffd: UFFD_FEATURE_WP_ZEROPAGE Peter Xu
2023-02-16 10:47 ` David Hildenbrand
2023-02-16 16:29 ` Peter Xu
2023-02-16 17:00 ` David Hildenbrand
2023-02-16 17:55 ` Peter Xu
2023-02-16 18:23 ` David Hildenbrand
2023-02-16 20:08 ` Peter Xu
2023-02-17 11:41 ` David Hildenbrand
2023-02-17 23:04 ` Peter Xu
2023-02-21 12:43 ` David Hildenbrand
2023-02-21 23:13 ` Peter Xu
2023-02-22 17:02 ` David Hildenbrand
2023-02-22 20:37 ` Peter Xu
2023-02-23 14:35 ` David Hildenbrand
2023-02-28 19:42 ` Peter Xu
2023-03-02 14:12 ` David Hildenbrand
2023-02-17 12:31 ` Muhammad Usama Anjum
2023-02-17 23:10 ` Peter Xu [this message]
2023-02-20 7:15 ` Muhammad Usama Anjum
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=Y/AJUi4o5hOKDkgy@x1n \
--to=peterx@redhat.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=axelrasmussen@google.com \
--cc=david@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=nadav.amit@gmail.com \
--cc=rppt@linux.vnet.ibm.com \
--cc=usama.anjum@collabora.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.