From: Breno Leitao <leitao@debian.org>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>, Liam.Howlett@oracle.com
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Liam R. Howlett" <Liam.Howlett@oracle.com>,
Vlastimil Babka <vbabka@suse.cz>,
kernel-team@meta.com, "open list:VMA" <linux-mm@kvack.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mm: Remove misleading 'unlikely' hint in vms_gather_munmap_vmas()
Date: Tue, 29 Oct 2024 04:52:32 -0700 [thread overview]
Message-ID: <20241029-discerning-outstanding-badger-6376bd@leitao> (raw)
In-Reply-To: <71b7cbeb-1301-491c-9637-e6d48938ddaf@lucifer.local>
On Fri, Oct 04, 2024 at 06:01:07PM +0100, Lorenzo Stoakes wrote:
> On Fri, Oct 04, 2024 at 09:48:31AM -0700, Breno Leitao wrote:
> > Performance analysis using branch annotation on a fleet of 200 hosts
> > running web servers revealed that the 'likely' hint in
>
> To be pedantic: *unlikely
>
> > vms_gather_munmap_vmas() was 100% consistently incorrect. In all
> > observed cases, the branch behavior contradicted the hint.
>
> OK so this is probably because vm_mmap_pgoff() declares the userfaultfd
> list head on the stack then passes it into do_mmap() and threads all the
> way to this code... and yeah, so that would be 100%.
>
> There are other code paths that aren't 100%, but the system call one is.
>
> Nice spot!
>
> >
> > Remove the 'unlikely' qualifier from the condition checking 'vms->uf'.
> > By doing so, we allow the compiler to make optimization decisions based
> > on its own heuristics and profiling data, rather than relying on a
> > static hint that has proven to be inaccurate in real-world scenarios.
>
> Yeah I'm generally not in favour of 'vibes' based likely()/unlikely(), I
> think it should always be based on profiling.
>
> It's understandable that there would be this expectation, and it may have
> migrated from other code that already had this check in where perhaps it
> wasn't always referencing a stack object, but yeah this is just wrong.
>
> >
> > Signed-off-by: Breno Leitao <leitao@debian.org>
>
> Liam will want a look too when he's back next week.
Liam, are you OK with this one? I suspect that Andrew is waiting for
your review before merging it.
>
> Looks good to me though!
>
> Reviewed-by: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>
>
> > ---
> > mm/vma.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/mm/vma.c b/mm/vma.c
> > index 4737afcb064c..9d4fe794dd07 100644
> > --- a/mm/vma.c
> > +++ b/mm/vma.c
> > @@ -1250,7 +1250,7 @@ int vms_gather_munmap_vmas(struct vma_munmap_struct *vms,
> > else if (is_data_mapping(next->vm_flags))
> > vms->data_vm += nrpages;
> >
> > - if (unlikely(vms->uf)) {
> > + if (vms->uf) {
> > /*
> > * If userfaultfd_unmap_prep returns an error the vmas
> > * will remain split, but userland will get a
> > --
> > 2.43.5
> >
next prev parent reply other threads:[~2024-10-29 11:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-04 16:48 Breno Leitao
2024-10-04 17:01 ` Lorenzo Stoakes
2024-10-29 11:52 ` Breno Leitao [this message]
2024-10-29 14:18 ` Liam R. Howlett
2024-10-07 11:50 ` Vlastimil Babka
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=20241029-discerning-outstanding-badger-6376bd@leitao \
--to=leitao@debian.org \
--cc=Liam.Howlett@oracle.com \
--cc=akpm@linux-foundation.org \
--cc=kernel-team@meta.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=vbabka@suse.cz \
/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