From: Davidlohr Bueso <dave@stgolabs.net>
To: Suren Baghdasaryan <surenb@google.com>
Cc: akpm@linux-foundation.org, willy@infradead.org,
liam.howlett@oracle.com, lorenzo.stoakes@oracle.com,
mhocko@suse.com, vbabka@suse.cz, hannes@cmpxchg.org,
mjguzik@gmail.com, oliver.sang@intel.com,
mgorman@techsingularity.net, david@redhat.com, peterx@redhat.com,
oleg@redhat.com, paulmck@kernel.org, brauner@kernel.org,
dhowells@redhat.com, hdanton@sina.com, hughd@google.com,
minchan@google.com, jannh@google.com, shakeel.butt@linux.dev,
souravpanda@google.com, pasha.tatashin@soleen.com,
corbet@lwn.net, linux-doc@vger.kernel.org, linux-mm@kvack.org,
linux-kernel@vger.kernel.org, kernel-team@android.com
Subject: Re: [PATCH v3 1/5] mm: introduce vma_start_read_locked{_nested} helpers
Date: Mon, 18 Nov 2024 08:57:51 -0800 [thread overview]
Message-ID: <20241118165751.3eqb5d4vobslkjpi@offworld> (raw)
In-Reply-To: <20241117080931.600731-2-surenb@google.com>
On Sun, 17 Nov 2024, Suren Baghdasaryan wrote:
>Introduce helper functions which can be used to read-lock a VMA when
>holding mmap_lock for read. Replace direct accesses to vma->vm_lock
>with these new helpers.
>
Reviewed-by: Davidlohr Bueso <dave@stgolabs.net>
>Signed-off-by: Suren Baghdasaryan <surenb@google.com>
next prev parent reply other threads:[~2024-11-18 16:58 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-17 8:09 [PATCH v3 0/5] move per-vma lock into vm_area_struct Suren Baghdasaryan
2024-11-17 8:09 ` [PATCH v3 1/5] mm: introduce vma_start_read_locked{_nested} helpers Suren Baghdasaryan
2024-11-18 13:07 ` Lorenzo Stoakes
2024-11-18 16:57 ` Davidlohr Bueso [this message]
2024-11-17 8:09 ` [PATCH v3 2/5] mm: move per-vma lock into vm_area_struct Suren Baghdasaryan
2024-11-18 13:24 ` Lorenzo Stoakes
2024-11-17 8:09 ` [PATCH v3 3/5] mm: mark vma as detached until it's added into vma tree Suren Baghdasaryan
2024-11-18 14:10 ` Lorenzo Stoakes
2024-11-18 16:23 ` Suren Baghdasaryan
2024-11-20 0:15 ` Suren Baghdasaryan
2024-11-17 8:09 ` [PATCH v3 4/5] mm: make vma cache SLAB_TYPESAFE_BY_RCU Suren Baghdasaryan
2024-11-18 14:05 ` Lorenzo Stoakes
2024-11-18 16:06 ` Suren Baghdasaryan
2024-11-17 8:09 ` [PATCH v3 5/5] docs/mm: document latest changes to vm_lock 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=20241118165751.3eqb5d4vobslkjpi@offworld \
--to=dave@stgolabs.net \
--cc=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=david@redhat.com \
--cc=dhowells@redhat.com \
--cc=hannes@cmpxchg.org \
--cc=hdanton@sina.com \
--cc=hughd@google.com \
--cc=jannh@google.com \
--cc=kernel-team@android.com \
--cc=liam.howlett@oracle.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mm@kvack.org \
--cc=lorenzo.stoakes@oracle.com \
--cc=mgorman@techsingularity.net \
--cc=mhocko@suse.com \
--cc=minchan@google.com \
--cc=mjguzik@gmail.com \
--cc=oleg@redhat.com \
--cc=oliver.sang@intel.com \
--cc=pasha.tatashin@soleen.com \
--cc=paulmck@kernel.org \
--cc=peterx@redhat.com \
--cc=shakeel.butt@linux.dev \
--cc=souravpanda@google.com \
--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