From: John Richard Moser <nigelenki@comcast.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Suspend to disk: do we HAVE to use swap?
Date: Tue, 31 Oct 2006 01:31:48 -0500 [thread overview]
Message-ID: <4546EDD4.70904@comcast.net> (raw)
In-Reply-To: <200610310716.40181.rjw@sisk.pl>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Rafael J. Wysocki wrote:
> On Tuesday, 31 October 2006 04:42, John Richard Moser wrote:
>> Something dumb came into my head, and the question is thus brought up
>> here: Do we HAVE to use swap for suspend to disk? How about the file
>> system?
>
> In short, we could use regular files for the suspend in the same way in which we
> use them for swap. Namely, we could bmap() a file and create a map of it
> (eg. with extents) that would be used for accessing the corresponding disk
> sectors at the block device level. Then, to be able to read the image the
> resume code would have to be provided with the number of the sector in which
> the suspend image header is located.
>
> However, we already have code that allows us to use swap files for the suspend
> and turning a regular file into a swap file is as easy as running 'mkswap' and
> 'swapon' on it.
And the kernel can survive being loaded, mounting a file system
readonly, activating swapon on the swap file on the read-only file
system, and then resuming from it?
Also, the file system is consistent after a suspend to disk?
I believe I mentioned something about compressing the image as well...
>
> Greetings,
> Rafael
>
>
- --
We will enslave their women, eat their children and rape their
cattle!
-- Bosc, Evil alien overlord from the fifth dimension
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.3 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iQIVAwUBRUbt0gs1xW0HCTEFAQL4nA/+JA7j+FHtmXYl2w/RpN/mZ+EMam++ippS
ildPeg/EsjdFLrc2SjmsteaPfCGokbLdA6WHwa5Uq+JB1Itu4rBLPRzvhVftm01V
XcYfInILhRNCGeGujF4P/NMFQBOPjPl1UqC+H/yehsVtj0I73ZMRDrdtI62+KWGL
ekaGKHb5rC3D0mdFOg/7ycplFbTLJii5Szn2KeHjd6+88LKbySLKv9SMPe6bMPPb
rzmy9+dzy3X/mMnWckxKyf6jFYkOXsI0GeNe/gb6Ylnpr6qNPJCPrY3MLSFKHPOA
Z7jBdS3w+glQhO0dUcsDSd9waPeOZNWGoJbq1FJIOMUiOU7fkoHVH7CNGGT+MccH
Qb8QxGhZUec77LmBAEKzpTi4R40QlHJaNHVip0NtOrTTupg+3J7SfDcDZ9frCRWa
hAs0/0sZV8y3ADtCf2bEOijj7zeLWRwSjTkj4fhXqcxlhEk030mKroYkohBGPIli
oVxRZq7nG4nY+dgNAxDCzFkyOEP5ObVq6dy7JPHfGOdPjy3gJy8cL/Y/6HxvzZIj
apHJznqz5+Bi7hFjG80++n7AzsM3RYzdWAh2OlcDM/jgZu7BypsGZ9QMkqTj6eDk
/Q11y+aj5+x4iYL2r+YrYlkhS3TIi2SUud05e8f87Di6nXiJfKLoFq6D6enU3v9M
xJ5l88pMfkQ=
=fs+p
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2006-10-31 6:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 3:42 Suspend to disk: do we HAVE to use swap? John Richard Moser
2006-10-31 6:16 ` Rafael J. Wysocki
2006-10-31 6:31 ` John Richard Moser [this message]
2006-10-31 6:39 ` Rafael J. Wysocki
2006-10-31 13:48 ` Alistair John Strachan
2006-10-31 17:40 ` Luca Tettamanti
2006-10-31 19:05 ` Alistair John Strachan
2006-10-31 19:19 ` Rafael J. Wysocki
2006-10-31 19:41 ` John Richard Moser
2006-10-31 20:04 ` Luca Tettamanti
2006-10-31 20:15 ` John Richard Moser
2006-10-31 21:20 ` Rafael J. Wysocki
2006-10-31 20:15 ` Luca Tettamanti
2006-10-31 21:18 ` Rafael J. Wysocki
2006-10-31 22:51 ` Luca Tettamanti
2006-10-31 22:31 ` Michael Lothian
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=4546EDD4.70904@comcast.net \
--to=nigelenki@comcast.net \
--cc=linux-kernel@vger.kernel.org \
--cc=rjw@sisk.pl \
/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