From: Pavel Machek <pavel@ucw.cz>
To: Nigel Cunningham <ncunningham@linuxmail.org>
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: Wed, 5 May 2004 12:11:58 +0200 [thread overview]
Message-ID: <20040505101158.GC1361@elf.ucw.cz> (raw)
In-Reply-To: <1083750907.17294.27.camel@laptop-linux.wpcb.org.au>
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.
And perhaps you want to write "What is swsusp2?" question/answer?
Pavel
--
934a471f20d6580d5aad759bf0d97ddc
next prev parent reply other threads:[~2004-05-05 10:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-05 9:47 swsusp documentation updates Pavel Machek
2004-05-05 9:55 ` Nigel Cunningham
2004-05-05 10:11 ` Pavel Machek [this message]
2004-05-05 21:03 ` Nigel Cunningham
2004-05-05 23:10 ` Nigel Cunningham
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
-- strict thread matches above, loose matches on Subject: below --
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=20040505101158.GC1361@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=akpm@zip.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@linuxmail.org \
--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