From: Lorenzo Stoakes <lstoakes@gmail.com>
To: Matthew Wilcox <willy@infradead.org>
Cc: Hyeonggon Yoo <42.hyeyoo@gmail.com>,
linux-mm@kvack.org, liam.howlett@oracle.com, surenb@google.com,
ldufour@linux.ibm.com, michel@lespinasse.org, vbabka@suse.cz,
linux-kernel@vger.kernel.org
Subject: Re: [QUESTION] about the maple tree and current status of mmap_lock scalability
Date: Thu, 29 Dec 2022 17:10:28 +0000 [thread overview]
Message-ID: <Y63KBNzdOkf3qmBX@murray> (raw)
In-Reply-To: <Y63FmaNoLAcdsLaU@casper.infradead.org>
On Thu, Dec 29, 2022 at 04:51:37PM +0000, Matthew Wilcox wrote:
> The mmap_lock is taken for many, many things. [snip]
I am currently describing the use of this lock (for 6.0) in the book and it is
striking just how broadly it's used. I'm diagramming it out for 'core' users,
i.e. non-driver and non-some other things, but even constraining that leaves a
HUGE number of users. I've also documented the 'unexpected' uses of the
page_table_lock, which seems to have been significantly improved over time but
still a few cases remain!
Am happy to give you (+ anybody else on MAINTAINERS list) an early copy of the
relevant bit (once I've finished the diagrams anyway) if that'd be helpful!
Now if you guys could stop obsoleting my work that'd be great ;)
next prev parent reply other threads:[~2022-12-29 17:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 12:48 Hyeonggon Yoo
2022-12-28 17:10 ` Suren Baghdasaryan
2022-12-29 11:33 ` Hyeonggon Yoo
2022-12-28 20:50 ` Matthew Wilcox
2022-12-29 14:22 ` Hyeonggon Yoo
2022-12-29 16:51 ` Matthew Wilcox
2022-12-29 17:10 ` Lorenzo Stoakes [this message]
2022-12-29 17:21 ` Suren Baghdasaryan
2022-12-29 17:31 ` Matthew Wilcox
2023-01-02 12:04 ` Hyeonggon Yoo
2023-01-02 14:37 ` Matthew Wilcox
2023-02-20 14:26 ` Hyeonggon Yoo
2023-02-20 14:43 ` Matthew Wilcox
2023-02-22 11:38 ` Hyeonggon Yoo
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=Y63KBNzdOkf3qmBX@murray \
--to=lstoakes@gmail.com \
--cc=42.hyeyoo@gmail.com \
--cc=ldufour@linux.ibm.com \
--cc=liam.howlett@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=michel@lespinasse.org \
--cc=surenb@google.com \
--cc=vbabka@suse.cz \
--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