On Fri, 6 Dec 2024 14:51:57 -0800 Suren Baghdasaryan <surenb@xxxxxxxxxx> 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@xxxxxxxxxx/ 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?
