Hi
In the scenario that 2GB physical RAM is available, and there is a
database application that eats 1.4GB RAM without leakage already
running, another leaker who leaks 4KB an hour is also running, could
the leaker be detected and killed in mm/oom_kill.c with default
configure when oom happens?
thanks
Hillf
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@xxxxxxxxxx For more info on Linux MM,
see: http://www.linux-mm.org/ .
Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/
Don't email: <a href=mailto:"dont@xxxxxxxxx";> email@xxxxxxxxx </a>