Re: [RFC PATCH RESEND 00/28] per-VMA locks proposal
From: Michal Hocko <mhocko@suse.com>
Date: 2022-09-05 12:39:27
Also in:
linux-arm-kernel, linux-mm, lkml
From: Michal Hocko <mhocko@suse.com>
Date: 2022-09-05 12:39:27
Also in:
linux-arm-kernel, linux-mm, lkml
Unless I am missing something, this is not based on the Maple tree rewrite, right? Does the change in the data structure makes any difference to the approach? I remember discussions at LSFMM where it has been pointed out that some issues with the vma tree are considerably simpler to handle with the maple tree. On Thu 01-09-22 10:34:48, Suren Baghdasaryan wrote: [...]
One notable way the implementation deviates from the proposal is the way VMAs are marked as locked. Because during some of mm updates multiple VMAs need to be locked until the end of the update (e.g. vma_merge, split_vma, etc).
I think it would be really helpful to spell out those issues in a greater detail. Not everybody is aware of those vma related subtleties. Thanks for working on this Suren! -- Michal Hocko SUSE Labs