From: Alexei Starovoitov <alexei.starovoitov@gmail.com>
To: Liam Howlett <liam.howlett@oracle.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Luigi Rizzo <lrizzo@google.com>, Yonghong Song <yhs@fb.com>,
Peter Zijlstra <peterz@infradead.org>,
Jason Gunthorpe <jgg@ziepe.ca>,
Daniel Borkmann <daniel@iogearbox.net>,
Michel Lespinasse <walken@google.com>, bpf <bpf@vger.kernel.org>,
"linux-mm@kvack.org" <linux-mm@kvack.org>,
Alexei Starovoitov <ast@kernel.org>,
Andrii Nakryiko <andrii@kernel.org>,
"kernel-team@fb.com" <kernel-team@fb.com>
Subject: Re: [PATCH mm/bpf v2] mm: bpf: add find_vma_no_check() without lockdep_assert on mm->mmap_lock
Date: Wed, 8 Sep 2021 12:42:12 -0700 [thread overview]
Message-ID: <20210908194212.ku7ysko4e4ecca2t@ast-mbp.dhcp.thefacebook.com> (raw)
In-Reply-To: <20210908184342.r3bwp7v24a6tnslg@revolver>
On Wed, Sep 08, 2021 at 06:43:49PM +0000, Liam Howlett wrote:
> * Alexei Starovoitov <alexei.starovoitov@gmail.com> [210908 14:03]:
> > On Wed, Sep 08, 2021 at 10:52:59AM -0700, Andrew Morton wrote:
> > > On Wed, 8 Sep 2021 10:21:18 -0700 Alexei Starovoitov <alexei.starovoitov@gmail.com> wrote:
> > >
> > > > > Again I am ignorant on the details so if you can clarify the following
> > > > > it may help me and others to better understand the problem:
> > > > >
> > > > > 1. Peter's patch appears to just take the same "fallback" path
> > > > > that would be taken if the trylock failed.
> > > > > Is this really a breakage or just loss of performance ?
> > > > > I would expect the latter, since it is called "fallback".
> > > >
> > > > As Yonghong explained it's a user space breakage.
> > > > User space tooling expects build_id to be available 99.999% of the time
> > > > and that's what users observed in practice.
> > > > They've built a bunch of tools on top of this feature.
> > > > The data from these tools goes into various datacenter tables
> > > > and humans analyze it later.
> > > > So Peter's proposal is not acceptable. We don't want to get yelled at.
> > > >
> > >
> > > I'm not understanding. Peter said "this patch merely removes a
> > > performance tweak" and you and Yonghong said "it breaks userspace".
> > > These assertions are contradictory!
> >
> > Peter said:
> > "The only sane approach is making the vma tree lockless, but so far the
> > bpf people have resisted doing the right thing because they've been
> > allowed to get away with these atrocities.
> > "
> > which is partially true.
> > bpf folks didn't resist it. There is work ongoing to make it lockless.
> > It just takes an long time. I don't see how bpf folks can speed it up
> > any further.
>
> What work are you doing on a lockless vma tree? I've been working on
> the maple tree and would like to hear what you've come up with.
Mainly cheering Michel and Paul from sidelines.
imo any approach would be better than the current state.
prev parent reply other threads:[~2021-09-08 19:42 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-08 4:44 Yonghong Song
2021-09-08 12:20 ` Daniel Borkmann
2021-09-08 13:53 ` Jason Gunthorpe
2021-09-08 14:15 ` Peter Zijlstra
2021-09-08 14:43 ` Luigi Rizzo
2021-09-08 15:12 ` Liam Howlett
2021-09-08 16:09 ` Yonghong Song
2021-09-08 17:09 ` Luigi Rizzo
2021-09-08 17:21 ` Alexei Starovoitov
2021-09-08 17:52 ` Andrew Morton
2021-09-08 18:02 ` Alexei Starovoitov
2021-09-08 18:15 ` Andrew Morton
2021-09-08 18:20 ` Alexei Starovoitov
2021-09-08 18:30 ` Liam Howlett
2021-09-08 18:45 ` Yonghong Song
2021-09-08 18:49 ` Jason Gunthorpe
2021-09-08 19:11 ` Yonghong Song
2021-09-08 23:33 ` Jason Gunthorpe
2021-09-09 5:50 ` Yonghong Song
2021-09-09 8:05 ` Peter Zijlstra
2021-09-08 18:43 ` Liam Howlett
2021-09-08 19:42 ` Alexei Starovoitov [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=20210908194212.ku7ysko4e4ecca2t@ast-mbp.dhcp.thefacebook.com \
--to=alexei.starovoitov@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=andrii@kernel.org \
--cc=ast@kernel.org \
--cc=bpf@vger.kernel.org \
--cc=daniel@iogearbox.net \
--cc=jgg@ziepe.ca \
--cc=kernel-team@fb.com \
--cc=liam.howlett@oracle.com \
--cc=linux-mm@kvack.org \
--cc=lrizzo@google.com \
--cc=peterz@infradead.org \
--cc=walken@google.com \
--cc=yhs@fb.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