From: Kefeng Wang <wangkefeng.wang@huawei.com>
To: Peter Xu <peterx@redhat.com>
Cc: Andrew Morton <akpm@linux-foundation.org>, <linux-mm@kvack.org>
Subject: Re: [PATCH v2] mm: memory: check userfaultfd_wp() in vmf_orig_pte_uffd_wp()
Date: Mon, 22 Apr 2024 10:13:33 +0800 [thread overview]
Message-ID: <9955f3e0-ec3e-4fcd-8f62-ffa52d371b2d@huawei.com> (raw)
In-Reply-To: <ZiUaZEHTyGr-nE4t@x1n>
[-- Attachment #1: Type: text/plain, Size: 1021 bytes --]
On 2024/4/21 21:53, Peter Xu wrote:
> On Sat, Apr 20, 2024 at 12:05:04PM +0800, Kefeng Wang wrote:
>> The latency of lat_pagefault increased a lot than the old kernel(vs 5.10),
>> except mm counter updating, the another obvious difference
>> shown from perf graph is the new vmf_orig_pte_uffd_wp().
>
> Curious how different it is.
>
It is not big, as shown in perf, only 0.1x% in the whole test, but it is
new added compared with old kernel.
Please check attached perf_0417_pagefault_x86.svg [with batch mm counter],
> I wanted to give it a quick shot over lmbench but fails on missing rpc.h,
> at least for the Intel repo. I think it's because of the libc change to
> drop that. Are you using a separate repo that fixed all things up?
yum install libtirpc-devel, I can build with it.
>
>> Moving it upper is better, and maybe add __always_inline to
>> vmf_orig_pte_uffd_wp() to make set_pte_range() only check VM_UFFD_WP from
>> vm_flags?
>
> Sounds good here, thanks.
OK, will update it too.
Thanks.
>
[-- Attachment #2: perf_0417_pagefault_x86.svg --]
[-- Type: image/svg+xml, Size: 103155 bytes --]
prev parent reply other threads:[~2024-04-22 2:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-18 12:06 [PATCH v2] mm: memory: check userfaultfd_wp() in vmf_orig_pte_uffd_wp() Kefeng Wang
2024-04-18 16:32 ` Peter Xu
2024-04-19 3:00 ` Kefeng Wang
2024-04-19 15:17 ` Peter Xu
2024-04-20 4:05 ` Kefeng Wang
2024-04-21 13:53 ` Peter Xu
2024-04-22 2:13 ` Kefeng Wang [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=9955f3e0-ec3e-4fcd-8f62-ffa52d371b2d@huawei.com \
--to=wangkefeng.wang@huawei.com \
--cc=akpm@linux-foundation.org \
--cc=linux-mm@kvack.org \
--cc=peterx@redhat.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.