From: Barry Song <21cnbao@gmail.com>
To: "Liam R. Howlett" <Liam.Howlett@oracle.com>,
Suren Baghdasaryan <surenb@google.com>,
Barry Song <21cnbao@gmail.com>,
lsf-pc@lists.linux-foundation.org, Linux-MM <linux-mm@kvack.org>,
Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
Matthew Wilcox <willy@infradead.org>,
David Hildenbrand <david@kernel.org>,
Oven <liyangouwen1@oppo.com>
Subject: Re: [LSM/MM/BPF TOPIC] Do not hold mmap_lock following folio_lock failure in page faults
Date: Thu, 26 Feb 2026 17:53:19 +0800 [thread overview]
Message-ID: <CAGsJ_4wNcXE-X5gVb72CUj2yOV-tbzZdmXM-5VXC9oG+NJWv-w@mail.gmail.com> (raw)
In-Reply-To: <hzrnxlu2ukoy5rmwrztrw7nk3icswtwup24jw5nqk2h5xf5crw@e3gqxyjf2pb7>
On Wed, Feb 25, 2026 at 5:21 AM Liam R. Howlett <Liam.Howlett@oracle.com> wrote:
>
> * Suren Baghdasaryan <surenb@google.com> [260224 12:14]:
[...]
> > >
> > > I would appreciate feedback from LSF/MM/BPF on approaches
> > > to eliminate mmap_lock acquisition in page faults triggered
> > > by folio_lock failure, for both I/O wait and PTE-mapping
> > > wait cases, for mainline inclusion.
> >
> > Would love to participate in this discussion. Hope Barry can attend in
> > person this time :)
>
> I would also like to participate in an in-person discussion about this.
>
> ...
Thank you very much to Suren and Liam for showing interest in this topic.
I’ll do my best to attend in person if the opportunity arises, though it’s
not yet 100% certain.
Thanks
Barry
prev parent reply other threads:[~2026-02-26 9:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-20 22:12 Barry Song
2026-02-24 17:14 ` Suren Baghdasaryan
2026-02-24 21:20 ` Liam R. Howlett
2026-02-26 9:53 ` Barry Song [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=CAGsJ_4wNcXE-X5gVb72CUj2yOV-tbzZdmXM-5VXC9oG+NJWv-w@mail.gmail.com \
--to=21cnbao@gmail.com \
--cc=Liam.Howlett@oracle.com \
--cc=david@kernel.org \
--cc=linux-mm@kvack.org \
--cc=liyangouwen1@oppo.com \
--cc=lorenzo.stoakes@oracle.com \
--cc=lsf-pc@lists.linux-foundation.org \
--cc=surenb@google.com \
--cc=willy@infradead.org \
/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