On 4/26/26 08:27, Suren Baghdasaryan wrote: > Use per-vma locks when reading /proc/pid/smaps and /proc/pid/numa_maps > similar to /proc/pid/maps to reduce contention on central mmap_lock. One > major difference between maps and smaps/numa_maps reading is that the > latter executes page table walk which can't be done under RCU due to a > possibility of sleeping. Therefore we drop RCU read lock before this walk > while keeping the VMA locked. After the walk we retake RCU read lock, > reset VMA iterator and proceed with the next VMA.
With many small VMAs, is that overhead noticable? -- Cheers, David
