> You fill up mem and you fill up swap, and you complain the box is
> acting funny ??
The kernel should save whatever memory it needs to do its work. It isn't
my problem, from userland, to worry that I take the last page in the
machine. If the kernel needs pages to operate efficiently, it had better
reserve them and not just hand them out until it locks up.
> This is a clear case of "Doctor it hurts when I ..." - Don't do it !
>
> I'm interested in hearing how you would accomplish graceful
> performance degradation in a situation where you have used up any
> possible resource on the machine. Transparent process back-tracking ?
> What ?
Gosh, here's an idea: if there is no memory left and someone malloc()s
some more, have malloc() fail? Kill the process that required the memory?
I can't believe the attitude I am hearing. Userland processes should be
able to go around doing whaever the fuck they want and the box should stay
alive. Currently, if a userland process runs amok, the kernel goes into
self-fucking mode for the rest of the week.
-jwb
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/