linux-mm.kvack.org archive mirror
 help / color / mirror / Atom feed
From: Qi Zheng <zhengqi.arch@bytedance.com>
To: Lorenzo Stoakes <lorenzo.stoakes@oracle.com>,
	Jann Horn <jannh@google.com>
Cc: Jonathan Corbet <corbet@lwn.net>,
	Andrew Morton <akpm@linux-foundation.org>,
	"Liam R . Howlett" <Liam.Howlett@oracle.com>,
	Vlastimil Babka <vbabka@suse.cz>,
	Alice Ryhl <aliceryhl@google.com>,
	Boqun Feng <boqun.feng@gmail.com>,
	Matthew Wilcox <willy@infradead.org>,
	Mike Rapoport <rppt@kernel.org>,
	linux-mm@kvack.org, linux-kernel@vger.kernel.org,
	Suren Baghdasaryan <surenb@google.com>,
	"open list:DOCUMENTATION" <linux-doc@vger.kernel.org>
Subject: Re: [RFC PATCH] docs/mm: add VMA locks documentation
Date: Wed, 6 Nov 2024 10:56:29 +0800	[thread overview]
Message-ID: <5969f498-a515-4394-a2b6-5d3abe2872aa@bytedance.com> (raw)
In-Reply-To: <2bf6329e-eb3b-4c5e-bd3a-b519eefffd63@lucifer.local>



On 2024/11/5 00:42, Lorenzo Stoakes wrote:
> On Sat, Nov 02, 2024 at 02:45:35AM +0100, Jann Horn wrote:
>> On Fri, Nov 1, 2024 at 7:50 PM Lorenzo Stoakes

[...]

>>> +
>>> +Page table locks
>>> +----------------

Many thanks to Lorenzo for documenting page table locks! This is really
needed. And at a glance, I agree with Jann's additions.

>>
>> (except last-level page tables: khugepaged already deletes those for
>> file mappings without using the mmap lock at all in
>> retract_page_tables(), and there is a pending series that will do the
>> same with page tables in other VMAs too, see
>> <https://lore.kernel.org/all/cover.1729157502.git.zhengqi.arch@bytedance.com/>)

Thanks to Jann for mentioning this series, I just updated it to v2
recently:

https://lore.kernel.org/lkml/cover.1730360798.git.zhengqi.arch@bytedance.com/

> 
> Ugh wut OK haha. Will look into this.

Thanks!



  parent reply	other threads:[~2024-11-06  2:56 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-01 18:50 Lorenzo Stoakes
2024-11-01 20:58 ` Lorenzo Stoakes
2024-11-01 22:41   ` Suren Baghdasaryan
2024-11-01 23:48   ` SeongJae Park
2024-11-04 13:02     ` Lorenzo Stoakes
2024-11-04 13:47       ` Mike Rapoport
2024-11-04 19:55         ` Lorenzo Stoakes
2024-11-02  1:45 ` Jann Horn
2024-11-04 16:42   ` Lorenzo Stoakes
2024-11-04 21:29     ` Jann Horn
2024-11-05 16:10       ` Lorenzo Stoakes
2024-11-05 17:21         ` Jann Horn
2024-11-06  3:09       ` Qi Zheng
2024-11-06 18:09         ` Jann Horn
2024-11-07  7:07           ` Qi Zheng
2024-11-06  2:56     ` Qi Zheng [this message]
2024-11-06 11:28       ` Lorenzo Stoakes
2024-11-07  6:47         ` Qi Zheng
2024-11-02  9:00 ` Mike Rapoport
2024-11-04 14:17   ` Lorenzo Stoakes
2024-11-04 15:19     ` Mike Rapoport
2024-11-05 12:23       ` Lorenzo Stoakes
2024-11-04 14:47 ` Alice Ryhl
2024-11-04 16:52   ` Lorenzo Stoakes
2024-11-05 13:56     ` Alice Ryhl
2024-11-05 14:18       ` Lorenzo Stoakes
2024-11-04 17:01 ` Suren Baghdasaryan
2024-11-04 21:04   ` Lorenzo Stoakes
2024-11-04 21:20     ` Suren Baghdasaryan
2024-11-05 16:11       ` Lorenzo Stoakes
2024-11-04 21:25     ` Jann Horn
2024-11-07 11:07 ` Hillf Danton
2024-11-07 11:15   ` Lorenzo Stoakes

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=5969f498-a515-4394-a2b6-5d3abe2872aa@bytedance.com \
    --to=zhengqi.arch@bytedance.com \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=aliceryhl@google.com \
    --cc=boqun.feng@gmail.com \
    --cc=corbet@lwn.net \
    --cc=jannh@google.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=lorenzo.stoakes@oracle.com \
    --cc=rppt@kernel.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