Re: Memory hogs
Hermann Schichl (herman@esi.ac.at)
Sat, 17 Jul 1999 18:17:53 +0200
Werner Almesberger wrote:
>
> > Hermann Schichl wrote:
> > I think it would be great if OOM handling would be
> > configurable (either kernel compile time or /proc interface)
>
> Better yet, have a device or proc file that becomes readable in this case.
> Then you can have a user-space demon to implement whatever policy you like.
> The demon can mlock its pages, so it should be reasonably safe from causing
> an OOM itself. Writing to that device/proc file could set the threshold for
> when OOM recovery is necessary.
>
Yes, I think this is the cleanest idea. And it could be expanded to most
limit-exceeding situations (num of processes,...).
>
> Reasonable policies may include enabling overflow swap space, SIGSTOP'ing
> all processes above a certain size/growth rate, paging the administrator,
> and opening a shell on the system console.
>
Where would be the proper place in the kernel-code to add such an interface?
- Hermann
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.rutgers.edu
Please read the FAQ at http://www.tux.org/lkml/