From: Nigel Cunningham <ncunningham@crca.org.au>
To: Pavel Machek <pavel@ucw.cz>
Cc: pm list <linux-pm@lists.linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>,
TuxOnIce-devel <tuxonice-devel@tuxonice.net>
Subject: Re: [linux-pm] [SUSPECTED SPAM] Re: Proposal for a new algorithm for reading & writing a hibernation image.
Date: Sat, 05 Jun 2010 10:20:55 +1000 [thread overview]
Message-ID: <4C099867.4050807@crca.org.au> (raw)
In-Reply-To: <9rpccea67yy402c975fqru8r.1275576653521@email.android.com>
Hi again.
As I think about this more, I reckon we could run into problems at
resume time with reloading the image. Even if some bits aren't modified
as we're writing the image, they still might need to be atomically
restored. If we make the atomic restore part too small, we might not be
able to do that.
So perhaps the best thing would be to stick with the way TuxOnIce splits
the image at the moment (page cache / process pages vs 'rest'), but
using this faulting mechanism to ensure we do get all the pages that are
changed while writing the first part of the image.
Regards,
Nigel
next prev parent reply other threads:[~2010-06-05 0:21 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-03 14:50 [SUSPECTED SPAM] Re: [linux-pm] Proposal for a new algorithm for reading & writing a hibernation image Pavel Machek
2010-06-04 23:39 ` Maxim Levitsky
2010-06-04 23:58 ` Nigel Cunningham
2010-06-05 0:36 ` Maxim Levitsky
2010-06-05 0:45 ` Maxim Levitsky
2010-06-05 3:37 ` Nigel Cunningham
2010-06-05 0:47 ` Nigel Cunningham
2010-06-05 1:16 ` Maxim Levitsky
2010-06-05 3:17 ` Nigel Cunningham
2010-06-05 0:05 ` Nigel Cunningham
2010-06-05 12:59 ` [TuxOnIce-devel] " Theodore Tso
2010-06-05 23:01 ` Nigel Cunningham
2010-06-05 0:20 ` Nigel Cunningham [this message]
2010-06-05 18:45 ` [linux-pm] [SUSPECTED SPAM] " Rafael J. Wysocki
2010-06-05 19:10 ` Maxim Levitsky
2010-06-05 19:21 ` Rafael J. Wysocki
2010-06-05 22:54 ` Nigel Cunningham
2010-06-05 23:20 ` Rafael J. Wysocki
2010-06-06 7:01 ` Nigel Cunningham
2010-06-06 14:06 ` Rafael J. Wysocki
2010-06-07 5:23 ` Nigel Cunningham
2010-06-07 8:40 ` Rafael J. Wysocki
2010-06-06 0:40 ` Maxim Levitsky
2010-06-06 13:57 ` Rafael J. Wysocki
2010-06-06 15:54 ` Maxim Levitsky
2010-06-06 19:04 ` Rafael J. Wysocki
2010-06-06 19:51 ` Maxim Levitsky
2010-06-06 21:55 ` Pedro Ribeiro
2010-06-07 8:41 ` Rafael J. Wysocki
2010-06-07 5:31 ` Nigel Cunningham
2010-06-07 8:49 ` Rafael J. Wysocki
2010-06-08 2:07 ` Nigel Cunningham
2010-06-08 9:01 ` Rafael J. Wysocki
2010-06-07 13:07 ` [TuxOnIce-devel] " Martin Steigerwald
2010-06-07 21:28 ` Rafael J. Wysocki
2010-06-07 21:31 ` Nigel Cunningham
2010-06-07 5:28 ` Nigel Cunningham
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=4C099867.4050807@crca.org.au \
--to=ncunningham@crca.org.au \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=pavel@ucw.cz \
--cc=tuxonice-devel@tuxonice.net \
/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