Re: [PATCH 2/3] mm: drop oom code from exit_mmap

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 5/9/22 9:00 PM, Suren Baghdasaryan wrote:
With the oom-killer being able to operate on locked pages, exit_mmap
does not need to ensure that oom_reap_task_mm is done before it can
proceed. Instead it can rely on mmap_lock write lock to prevent
oom-killer from operating on the vma tree while it's freeing page
tables. exit_mmap can hold mmap_lock read lock when unmapping vmas
and then take mmap_lock write lock before freeing page tables.

Signed-off-by: Suren Baghdasaryan <surenb@xxxxxxxxxx>
---
  include/linux/oom.h |  2 --
  mm/mmap.c           | 25 ++++++-------------------
  mm/oom_kill.c       |  2 +-
  3 files changed, 7 insertions(+), 22 deletions(-)


How does this improve the test? Include the information on why this
change is needed as opposed describing what this does?

thanks,
-- Shuah




[Index of Archives]     [Linux ARM Kernel]     [Linux ARM]     [Linux Omap]     [Fedora ARM]     [IETF Annouce]     [Bugtraq]     [Linux OMAP]     [Linux MIPS]     [eCos]     [Asterisk Internet PBX]     [Linux API]

  Powered by Linux