From: Nigel Cunningham <ncunningham@clear.net.nz>
To: "Linux Memory Management List (E-mail)" <linux-mm@kvack.org>
Subject: Using reverse mapping in 2.5.51 for suspend-to-disk.
Date: Wed, 11 Dec 2002 19:44:29 +1300 [thread overview]
Message-ID: <000101c2a0e0$c5743140$ac99a7cb@NigelLaptop> (raw)
Hi all.
Let me begin by saying I'm quite new to kernel hacking, and will freely
admit that I've lots still to learn. Please, therefore, cut me some slack if
I show previously unsurpassed ignorance!
First, some background:
I've done some work on the suspend-to-disk code in the 2.4 series kernels.
The mainstream suspend-to-disk code in 2.4 essentially eats all the memory
it can, makes a copy of the remainder, and writes that copy to disk. I
prepared a version that eats far less memory and writes a bigger image,
thereby resulting in a more responsive system on resume (although it takes
longer to read). The target, of course is to eat [virtually] no memory at
all and store as close to a perfect image as possible. To get closer to
that, I implemented a crude reverse mapping (assuming I understand the term
correctly) which makes a bitmap of pages ('pageset 1') that are only used by
processes which have been stopped (ie processes not needed for writing the
image), writes the contents of those pages to disk and then copies and saves
the remaining pages ('pageset 2') using pageset1 pages and free memory. It
works well, and will probably work better once I put it in a kernel where
drivers are properly quiesced!
Which brings me to my question. I want to start trying to get this going in
a 2.5 kernel, and have seen people talking about reverse-mapping patches for
a while now. I'm wondering if you have managed or are preparing to merge
such patches into the 2.5 series, whether they would be helpful to me in
identifying those pageset1 pages. If so, how I use them.
Of course you might want to bag the whole method in general :> I'll happily
try to implement a better method if you suggestion one!
Regards and thanks in advance,
Nigel
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/
next reply other threads:[~2002-12-11 6:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-11 6:44 Nigel Cunningham [this message]
2002-12-11 13:22 ` Rik van Riel
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='000101c2a0e0$c5743140$ac99a7cb@NigelLaptop' \
--to=ncunningham@clear.net.nz \
--cc=linux-mm@kvack.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox