All of lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Wilcox <willy@infradead.org>
To: "Lorenzo Stoakes (ARM)" <ljs@kernel.org>
Cc: Suren Baghdasaryan <surenb@google.com>,
	akpm@linux-foundation.org, dave.hansen@linux.intel.com,
	Liam.Howlett@oracle.com, david@kernel.org,
	shakeel.butt@linux.dev, vbabka@kernel.org, jannh@google.com,
	aliceryhl@google.com, arve@android.com, cmllamas@google.com,
	christian@brauner.io, tkjos@android.com, dsahern@kernel.org,
	davem@davemloft.net, gregkh@linuxfoundation.org,
	linux-kernel@vger.kernel.org, linux-mm@kvack.org,
	netdev@vger.kernel.org
Subject: Re: [PATCH v4 1/5] mm: Make per-VMA locks available universally
Date: Mon, 10 Aug 2026 16:56:42 +0100	[thread overview]
Message-ID: <ann0urrWGUqQsHyq@casper.infradead.org> (raw)
In-Reply-To: <anmTYW8X6c9TgaO0@lucifer>

On Mon, Aug 10, 2026 at 11:17:26AM +0100, Lorenzo Stoakes (ARM) wrote:
> And, in general, having consistent per-arch fault logic would be a good
> thing (TM) (and particularly - as Matthew intends to do - having shared
> code for this is a _really_ good idea, the duplication right now is
> horrible).
> 
> So perhaps Matthew could do this as part of his changes or you could follow
> up with changes to do that?
> 
> I think his work would be made easier by this being the same everywhere,
> however.

Yes, having per-VMA locks everywhere is kind of essential, so I was
planning on going second after this was merged.  Hence the careful
review ;-)



  parent reply	other threads:[~2026-08-10 15:57 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-06 20:05 [PATCH v4 0/5] mm: Unconditional per-VMA locks and cleanups Suren Baghdasaryan
2026-08-06 20:05 ` [PATCH v4 1/5] mm: Make per-VMA locks available universally Suren Baghdasaryan
2026-08-07 15:37   ` Vlastimil Babka (SUSE)
2026-08-08  1:12   ` Matthew Wilcox
2026-08-08  6:08     ` Suren Baghdasaryan
2026-08-10  8:52     ` Lorenzo Stoakes (ARM)
2026-08-10  9:42       ` Lorenzo Stoakes (ARM)
2026-08-10 16:40         ` Suren Baghdasaryan
2026-08-10 10:17   ` Lorenzo Stoakes (ARM)
2026-08-10 15:22     ` Dave Hansen
2026-08-10 15:56     ` Matthew Wilcox [this message]
2026-08-10 17:04     ` Suren Baghdasaryan
2026-08-06 20:05 ` [PATCH v4 2/5] binder: Make shrinker rely solely on per-VMA lock Suren Baghdasaryan
2026-08-07 14:26   ` Alice Ryhl
2026-08-10 10:22   ` Lorenzo Stoakes (ARM)
2026-08-10 18:32   ` Carlos Llamas
2026-08-10 18:54     ` Suren Baghdasaryan
2026-08-10 19:16       ` Carlos Llamas
2026-08-10 21:00         ` Suren Baghdasaryan
2026-08-10 18:57     ` Carlos Llamas
2026-08-06 20:05 ` [PATCH v4 3/5] mm: Add RCU-based VMA lookup helper that waits for writers Suren Baghdasaryan
2026-08-07 15:39   ` Vlastimil Babka (SUSE)
2026-08-08  7:24   ` Matthew Wilcox
2026-08-09  1:07     ` Suren Baghdasaryan
2026-08-10 10:24       ` Lorenzo Stoakes (ARM)
2026-08-10 15:25         ` Dave Hansen
2026-08-08  7:37   ` Matthew Wilcox
2026-08-10 10:41   ` Lorenzo Stoakes (ARM)
2026-08-10 17:07     ` Suren Baghdasaryan
2026-08-06 20:05 ` [PATCH v4 4/5] binder: Remove mmap_lock fallback Suren Baghdasaryan
2026-08-06 20:05 ` [PATCH v4 5/5] tcp: Remove mmap_lock fallback path Suren Baghdasaryan
2026-08-08  7:26   ` Matthew Wilcox
2026-08-09  0:51     ` Suren Baghdasaryan
2026-08-10 15:26       ` Dave Hansen
2026-08-10 17:09         ` Suren Baghdasaryan

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=ann0urrWGUqQsHyq@casper.infradead.org \
    --to=willy@infradead.org \
    --cc=Liam.Howlett@oracle.com \
    --cc=akpm@linux-foundation.org \
    --cc=aliceryhl@google.com \
    --cc=arve@android.com \
    --cc=christian@brauner.io \
    --cc=cmllamas@google.com \
    --cc=dave.hansen@linux.intel.com \
    --cc=davem@davemloft.net \
    --cc=david@kernel.org \
    --cc=dsahern@kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=jannh@google.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mm@kvack.org \
    --cc=ljs@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=shakeel.butt@linux.dev \
    --cc=surenb@google.com \
    --cc=tkjos@android.com \
    --cc=vbabka@kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.