From: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
To: Jinjie Ruan <ruanjinjie@huawei.com>
Cc: viro@zeniv.linux.org.uk, brauner@kernel.org, jack@suse.cz,
akpm@linux-foundation.org, Liam.Howlett@oracle.com,
lokeshgidra@google.com, rppt@kernel.org, aarcange@redhat.com,
Jason@zx2c4.com, linux-fsdevel@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-mm@kvack.org
Subject: Re: [PATCH 0/2] userfaultfd: handle few NULL check inline
Date: Mon, 9 Dec 2024 13:42:41 +0000 [thread overview]
Message-ID: <f7f1b152-3f25-4df3-9589-2fceb6d18613@lucifer.local> (raw)
In-Reply-To: <20241209132549.2878604-1-ruanjinjie@huawei.com>
On Mon, Dec 09, 2024 at 09:25:47PM +0800, Jinjie Ruan wrote:
> Handle dup_userfaultfd() and anon_vma_fork() NULL check inline to
> save some function call overhead. The Unixbench single core process
> create has 1% improve with these patches.
>
> Jinjie Ruan (2):
> userfaultfd: handle dup_userfaultfd() NULL check inline
> mm, rmap: handle anon_vma_fork() NULL check inline
>
> fs/userfaultfd.c | 5 +----
> include/linux/rmap.h | 12 +++++++++++-
> include/linux/userfaultfd_k.h | 11 ++++++++++-
> mm/rmap.c | 6 +-----
> 4 files changed, 23 insertions(+), 11 deletions(-)
>
> --
> 2.34.1
>
Coincidentally I've just diagosed a rather nasty bug in this code [0], so
could we hold off on this change for just a little bit until we can get a
fix out for this please?
I'd rather not complicate anything until we're sure we won't need to change
this.
Thanks!
[0]:https://lore.kernel.org/linux-mm/aa2c1930-becc-4bc5-adfb-96e88290acc7@lucifer.local/
next prev parent reply other threads:[~2024-12-09 13:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-09 13:25 Jinjie Ruan
2024-12-09 13:25 ` [PATCH 1/2] userfaultfd: handle dup_userfaultfd() " Jinjie Ruan
2024-12-09 13:25 ` [PATCH 2/2] mm, rmap: handle anon_vma_fork() " Jinjie Ruan
2024-12-09 13:35 ` Matthew Wilcox
2024-12-10 2:25 ` Jinjie Ruan
2024-12-09 13:42 ` Lorenzo Stoakes [this message]
2024-12-10 1:21 ` [PATCH 0/2] userfaultfd: handle few " Jinjie Ruan
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=f7f1b152-3f25-4df3-9589-2fceb6d18613@lucifer.local \
--to=lorenzo.stoakes@oracle.com \
--cc=Jason@zx2c4.com \
--cc=Liam.Howlett@oracle.com \
--cc=aarcange@redhat.com \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=jack@suse.cz \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lokeshgidra@google.com \
--cc=rppt@kernel.org \
--cc=ruanjinjie@huawei.com \
--cc=viro@zeniv.linux.org.uk \
/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