lkml.org 
[lkml]   [2016]   [Feb]   [3]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    Subject[PATCH 0/5] oom reaper v5
    Date
    Hi,
    I am reposting the whole patchset on top of mmotm with the previous
    version of the patchset reverted for an easier review. The series
    applies cleanly on top of the current Linus tree as well.

    The previous version was posted http://lkml.kernel.org/r/1452094975-551-1-git-send-email-mhocko@kernel.org
    I have tried to address most of the feedback. There was some push
    for extending the current implementation further but I do not feel
    comfortable to do that right now. I believe that we should start
    as easy as possible and add extensions on top. That shouldn't be
    hard with the current architecture.

    Wrt. the previous version, I have added patches 4 and 5. Patch4 reports
    success/failures to reap a task which is useful to see how the reaper
    operates. Patch 5 is implementing a more robust API between the oom
    killer and the oom reaper. We allow more tasks to be queued for the
    reaper at the same time rather than the original signle task mode.

    Patch 1 also dropped oom_reaper thread priority handling as per
    David. I ended up keeping vma filtering code inside __oom_reap_task.
    I still believe this is a better fit because the rules are a single
    fit for the reaper. They cannot be shared with a larger code base.

    In the meantime I have prepared down_write_killable rw_semaphore
    variant http://lkml.kernel.org/r/1454444369-2146-1-git-send-email-mhocko@kernel.org
    and also have a tentative patch to convert some users of mmap_sem for
    write to use the killable version. This needs more checking though but
    I guess I will have something ready in 2 weeks or so (I will be on
    vacation next week).

    For the general description of the oom_reaper functionality, please
    refer to Patch1.

    I would be really greatful if we could postpone any
    functional/semantical enhancements for later discussion and focus on the
    correctness of these particular patches as there were no fundamental
    objectios to the current approach.

    Thanks!

    \
     
     \ /
      Last update: 2016-02-03 15:01    [W:4.028 / U:0.028 seconds]
    ©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site