> Well, but if all the swaps gets used, you go OOM and randomly kill
> processes. That means that machines have way more swap than they need.
>
> If you really want to "solve" it reliably, you can always
>
> swapon /dev/hdfoo666
>
> where hdfoo666 is as big as ram, just before starting swsusp. We could
> even make swapon part of swsusp where its locked to kill races.
>
> But I believe its not needed. Problem just is not there in practise.
OK, well suppose RAM is full, and swap is almost full (less than used
RAM left). System is still running fine, no OOM. But suspend can't work,
AFAICS.
Saving a separate area to save RAM into seems like the only deterministic
method to me.
M.
-
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/
This archive was generated by hypermail 2b29 : Wed Apr 23 2003 - 22:00:39 EST