One sane unification case
Posted Jul 20, 2007 11:54 UTC (Fri) by farnz
In reply to: Yet another approach to software suspend
Parent article: Yet another approach to software suspend
There is one interesting unification setup (which can be implemented later, once we've got S2RAM and hibernation working well): hibernate, then (without damaging the hibernate state, so that we can resume again if needed), resume into S2RAM. If we restart running from S2RAM, great, we've just had a nice fast resume. If we lose power, so that we can't resume from S2RAM, ah well, time to restore from hibernate.
It's a limited use case, but one that some people could benefit from; I can think of the following times when I'd want it:
- When leaving my desktop alone for an extended period; if power is stable, I want a fast resume. If power goes on me, it'd be nice to still get a resume.
- When my server's UPS tells it that it's low on battery and lacking mains input. If the outage lasts only another 10 minutes, resuming from S2RAM (via USB signalling or similar) is quicker than coming back from hibernate.
- When I'm closing my laptop at the end of the day to travel home; if I've got enough battery to hold me in S2RAM, I'd like the fast resume when I'm next working. If I don't, I'd still prefer resume from disk to rebooting.
As you can see, all of these are unusual use cases, and S2RAM is just an optimization; I'd cope with having to do hibernate for every case.
to post comments)