diff options
author | Rafael J. Wysocki <rjw@sisk.pl> | 2006-06-23 02:04:48 -0700 |
---|---|---|
committer | Linus Torvalds <torvalds@g5.osdl.org> | 2006-06-23 07:43:00 -0700 |
commit | 968808b8956e332e556b1eae9b4f7df77518f53b (patch) | |
tree | e90598c5640df24a250aa0beb3e526f2571ed6e2 /arch/x86_64/kernel | |
parent | 7bff24e255ee11ecbc304315a252fcbd84f9ffce (diff) | |
download | blackbird-op-linux-968808b8956e332e556b1eae9b4f7df77518f53b.tar.gz blackbird-op-linux-968808b8956e332e556b1eae9b4f7df77518f53b.zip |
[PATCH] swsusp: use less memory during resume
Make swsusp allocate only as much memory as needed to store the image data
and metadata during resume.
Without this patch swsusp additionally allocates many page frames that will
conflict with the "original" locations of the image data and are considered
as "unsafe", treating them as "eaten" pages (ie. allocated but unusable).
The patch makes swsusp allocate as many pages as it'll need to store the
data read from the image in one shot, creating a list of allocated "safe"
pages, and use the observation that all pages allocated by it are marked
with the PG_nosave and PG_nosave_free flags set. Namely, when it's about
to load an image page, swsusp can check whether the page frame
corresponding to the "original" location of this page has been allocated
(ie. if the page frame has the PG_nosave and PG_nosave_free flags set) and
if so, it can load the page directly into this page frame. Otherwise it
uses an allocated "safe" page from the list to store the data that will be
copied to their "original" location later on.
This allows us to save many page copyings and page allocations during
resume and in the future it may allow us to load images greater than 50% of
the normal zone.
Signed-off-by: Rafael J. Wysocki <rjw@sisk.pl>
Acked-by: "Pavel Machek" <pavel@suse.cz>
Signed-off-by: Andrew Morton <akpm@osdl.org>
Signed-off-by: Linus Torvalds <torvalds@osdl.org>
Diffstat (limited to 'arch/x86_64/kernel')
0 files changed, 0 insertions, 0 deletions