From: Nigel Cunningham <ncunningham@linuxmail.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Andrew Morton <akpm@zip.com.au>,
Rusty trivial patch monkey Russell <trivial@rustcorp.com.au>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: swsusp documentation updates
Date: Thu, 06 May 2004 09:10:26 +1000 [thread overview]
Message-ID: <1083798626.17294.79.camel@laptop-linux.wpcb.org.au> (raw)
In-Reply-To: <20040505101158.GC1361@elf.ucw.cz>
Hi.
On Wed, 2004-05-05 at 20:11, Pavel Machek wrote:
> Hi!
>
> > > +There are two solutions to this:
> > > +
> > > +* require half of memory to be free during suspend. That way you can
> > > +read "new" data onto free spots, then cli and copy
> >
> > Would you consider adding:
> >
> > (Suspend2, which allows more than half of memory to be saved, is a
> > variant on this).
>
> How would you like this added?
>
> swsusp2 shares this fundamental limitation, but does not include user
> data and disk caches into "used memory" by saving them in
> advance. That means that limitation goes away in practice.
That sounds good. I'd include that.
> And perhaps you want to write "What is swsusp2?" question/answer?
How does this sound?...
What is 'swsusp2'?
swsusp2 is Software Suspend 2, forked implementation of suspend-to-disk
which is available as separate patches for 2.4 and 2.6 kernels from
swsusp.sourceforge.net. It includes support for SMP, 4GB Highmem and
preemption. It also has a extensible architecture that allows for
arbitrary transformations on the image (compression, encryption) and
arbitrary backends for writing the image (eg to swap or an NFS
share[Work In Progress]). Questions regarding suspend2 should be sent to
the mailing list available through the Suspend2 website, and not to the
Linux Kernel Mailing List. We are working toward merging Suspend2 into
the mainline kernel.
--
Nigel & Michelle Cunningham
C/- Westminster Presbyterian Church Belconnen
61 Templeton Street, Cook, ACT 2614.
+61 (2) 6251 7727(wk); +61 (2) 6254 0216 (home)
Evolution (n): A hypothetical process whereby infinitely improbable events occur
with alarming frequency, order arises from chaos, and no one is given credit.
next prev parent reply other threads:[~2004-05-05 23:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-05 9:47 Pavel Machek
2004-05-05 9:55 ` Nigel Cunningham
2004-05-05 10:11 ` Pavel Machek
2004-05-05 21:03 ` Nigel Cunningham
2004-05-05 23:10 ` Nigel Cunningham [this message]
2004-05-11 2:51 ` Pavel Machek
2004-05-11 22:45 ` Nigel Cunningham
2004-05-05 11:00 ` Romano Giannetti
2004-05-05 11:09 ` Pavel Machek
2004-05-05 21:43 Karol Kozimor
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=1083798626.17294.79.camel@laptop-linux.wpcb.org.au \
--to=ncunningham@linuxmail.org \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=trivial@rustcorp.com.au \
/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
all inboxes | Powered by JetHome®