On Thu, 24 Apr 2003 07:41:11 +1200
Nigel Cunningham <ncunningham@clear.net.nz> wrote:
> Swsusp will use the portion of your swap partition that is unused when
> you start to suspend. The version currently in the 2.5 tree frees most
> of your memory before suspending, and so doesn't need that much swap at
> all. The version that I'm working on merging only frees memory if it is
> necessary to fit the image in the available swap or to have enough
> memory to be able to save the image. Thus, you need a lot more swap for
> my version. (eg. I have 640MB ram on my laptop and a ~700MB swap
> partition).
>
Ok! I see the advantages / disadvantages of each version. But what happens if the memory AND swap space are full and nothing can't be freed? When I watch the memory and swap consumption on my laptop, I think it's the most time the case...
Another question:
Is it a big problem to save the memory in a separate file on the file system, and save somewhere the pointer to it (as example in swap. Also we could set a flag in swap so that we now that the last shutdown was a hybernation). One Problem will be, that we don't know the filesystem type on resume...(We could save the module in swap...)
All that is just theoretical. It's only a idea.
Thank you for your statements.
greets
Marc
-
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/