From: Andrew Morton <akpm@linux-foundation.org>
To: Suren Baghdasaryan <surenb@google.com>
Cc: 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, dave@stgolabs.net, 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,
Peter Zijlstra <peterz@infradead.org>
Subject: Re: [PATCH v5 0/6] move per-vma lock into vm_area_struct
Date: Fri, 6 Dec 2024 20:29:04 -0800 [thread overview]
Message-ID: <20241206202904.e685764837504d97cbc3cf62@linux-foundation.org> (raw)
In-Reply-To: <20241206225204.4008261-1-surenb@google.com>
On Fri, 6 Dec 2024 14:51:57 -0800 Suren Baghdasaryan <surenb@google.com> wrote:
> Back when per-vma locks were introduces, vm_lock was moved out of
> vm_area_struct in [1] because of the performance regression caused by
> false cacheline sharing. Recent investigation [2] revealed that the
> regressions is limited to a rather old Broadwell microarchitecture and
> even there it can be mitigated by disabling adjacent cacheline
> prefetching, see [3].
>
> ...
>
> Patch applies over linux-next (due to vm_lock change [5] not in mm tree).
>
> ...
>
> [5] https://lore.kernel.org/all/20241122174416.1367052-2-surenb@google.com/
Well that's awkward. I added the "seqlock: add raw_seqcount_try_begin"
series to mm.git. Peter, please drop your copy from linux-next?
prev parent reply other threads:[~2024-12-07 4:29 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-06 22:51 Suren Baghdasaryan
2024-12-06 22:51 ` [PATCH v5 1/6] mm: introduce vma_start_read_locked{_nested} helpers Suren Baghdasaryan
2024-12-10 9:03 ` Vlastimil Babka
2024-12-06 22:51 ` [PATCH v5 2/6] mm: move per-vma lock into vm_area_struct Suren Baghdasaryan
2024-12-10 9:15 ` Vlastimil Babka
2024-12-06 22:52 ` [PATCH v5 3/6] mm: mark vma as detached until it's added into vma tree Suren Baghdasaryan
2024-12-10 9:35 ` Vlastimil Babka
2024-12-10 11:36 ` Vlastimil Babka
2024-12-10 16:28 ` Suren Baghdasaryan
2024-12-06 22:52 ` [PATCH v5 4/6] mm: make vma cache SLAB_TYPESAFE_BY_RCU Suren Baghdasaryan
2024-12-09 17:35 ` Klara Modin
2024-12-09 20:28 ` Suren Baghdasaryan
2024-12-09 22:19 ` Suren Baghdasaryan
2024-12-10 12:06 ` Vlastimil Babka
2024-12-10 16:23 ` Suren Baghdasaryan
2024-12-10 14:21 ` Vlastimil Babka
2024-12-10 16:20 ` Suren Baghdasaryan
2024-12-10 16:32 ` Vlastimil Babka
2024-12-10 17:16 ` Suren Baghdasaryan
2024-12-10 17:25 ` Vlastimil Babka
2024-12-10 18:53 ` Suren Baghdasaryan
2024-12-10 23:01 ` Suren Baghdasaryan
2024-12-11 15:30 ` Suren Baghdasaryan
2024-12-11 16:05 ` Vlastimil Babka
2024-12-11 16:14 ` Suren Baghdasaryan
2024-12-06 22:52 ` [PATCH v5 5/6] mm/slab: allow freeptr_offset to be used with ctor Suren Baghdasaryan
2024-12-10 11:01 ` Vlastimil Babka
2024-12-06 22:52 ` [PATCH v5 6/6] docs/mm: document latest changes to vm_lock Suren Baghdasaryan
2024-12-07 3:23 ` Randy Dunlap
2024-12-07 4:24 ` Akira Yokosawa
2024-12-07 17:33 ` Suren Baghdasaryan
2024-12-07 4:29 ` Andrew Morton [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=20241206202904.e685764837504d97cbc3cf62@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=brauner@kernel.org \
--cc=corbet@lwn.net \
--cc=dave@stgolabs.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=peterz@infradead.org \
--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