[lkml]   [2005]   [Jan]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
    SubjectRe: User space out of memory approach
    On Tue, Jan 11, 2005 at 10:30:46AM +0100, Thomas Gleixner wrote:
    > > > > 2) killing just gets the first candidate from the list and kills it.
    > > > > No need to calculate
    > > > > at kernel level.
    > So I need a userspace change in order to solve a kernel problem ?

    Allowing userspace to tune is a great idea. However we cannot invoke
    userland at oom-time to make the decision, or it would be deadlock prone
    (userland may be swapped out or it might require minor allocations of
    memory, if we were to allow userspace to do the decision it would be
    required to be a mlockall userland and not allowed to do syscalls, and
    even then it could mess up with the stack or signal handlers). So the
    safe thing to do is to assign different ratings to different userspace
    tasks. Of course this is inherited from the childs. That is a reasonable
    approach IMHO. Kurt wrote that patch, I only ported it to a more recent

    This way you can rate your important services and the not important

    Anyway as you've mentioned in a earlier email, there were more
    fundamental problems than the selection algorithm, the userspace rating
    was the lowest one in the prio list.
    To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
    the body of a message to
    More majordomo info at
    Please read the FAQ at

     \ /
      Last update: 2005-03-22 14:09    [W:0.019 / U:23.356 seconds]
    ©2003-2017 Jasper Spaans. hosted at Digital OceanAdvertise on this site