> So why not have a mechanism by which the user's desktop environment and init / login system can reserve itself enough memory to always be responsive under an

> So why not have a mechanism by which the user's desktop environment and init / login system can reserve itself enough memory to always be responsive under any memory condition? This! Always wanted a /proc/$PID flag to flag process' pages never to go to swap and reserve a number of cache pages specifically for the process. Something similar to mlock.