public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Martin Dalecki <dalecki@evision-ventures.com>
To: Linus Torvalds <torvalds@transmeta.com>
Cc: Pavel Machek <pavel@ucw.cz>,
	kernel list <linux-kernel@vger.kernel.org>,
	ACPI mailing list <acpi-devel@lists.sourceforge.net>
Subject: Re: suspend-to-{RAM,disk} for 2.5.17
Date: Wed, 22 May 2002 08:49:55 +0200	[thread overview]
Message-ID: <3CEB3F93.7030508@evision-ventures.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0205211557410.1307-100000@penguin.transmeta.com>

Uz.ytkownik Linus Torvalds napisa?:
> On Wed, 22 May 2002, Pavel Machek wrote:
> 
>>Major parts are: process stopper, S3 specific code, S4 specific
>>code. What can I do to make this applied?
> 
> 
> Applied. Nothing needed but some time for me to look through it.
> 
> It still has a few too many #ifdef CONFIG_SUSPEND, and I get this feeling 
> that the background deamons shouldn't need to do the "freeze()" by hand 
> but simply be automatically frozen and thawed when they sleep by looking 
> at the KERNTHREAD bit or something, but..

Oh and please reject the idea of compressing the pages
you are writing to disk for the following reaons:

1. compression is not deterministic in terms of the possible space
savings, you will still have to provide the required amount of space.

2. every compression algorithm has theoretical cases where the
compression mechanism is actually increasing the space requirements.

3. Compressing around 360 Mbytes of data will take quite a lot
of time.

4. Point 3 will make the CPU go high - not nice if the suspend
happens in case of battery emergency...

Anyway it's time to repartition my notebook :-).


  parent reply	other threads:[~2002-05-22  7:53 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-05-21 22:28 suspend-to-{RAM,disk} for 2.5.17 Pavel Machek
2002-05-21 23:01 ` Linus Torvalds
2002-05-21 23:15   ` Linus Torvalds
2002-05-21 23:27     ` Pavel Machek
2002-05-21 23:40     ` Pavel Machek
2002-05-21 23:20   ` Pavel Machek
2002-05-21 23:26     ` Linus Torvalds
2002-05-21 23:33       ` Pavel Machek
2002-05-22  0:09         ` Linus Torvalds
2002-05-22  0:15           ` Pavel Machek
2002-05-22  6:49   ` Martin Dalecki [this message]
2002-05-22  9:00     ` Pavel Machek
2002-05-22 10:03     ` Xavier Bestel
2002-05-22  9:03       ` Martin Dalecki
2002-05-22 10:35         ` Albert D. Cahalan
2002-05-22 10:42         ` Xavier Bestel
2002-05-22 12:54       ` Frank v Waveren
2002-05-22 15:59       ` Linus Torvalds
2002-05-25 13:30 ` Geert Uytterhoeven
2002-05-26 17:20   ` Pavel Machek
2002-05-27 19:40 ` William Lee Irwin III
2002-05-28 19:20   ` Pavel Machek
2002-05-28 19:32   ` Pavel Machek
2002-05-28 21:09     ` William Lee Irwin III
2002-05-28 21:11       ` Pavel Machek
2002-05-28 21:24         ` William Lee Irwin III
2002-05-28 21:34           ` Pavel Machek
2002-05-28 21:53             ` William Lee Irwin III
2002-05-28 22:00               ` Pavel Machek
2002-05-28 22:28                 ` William Lee Irwin III

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=3CEB3F93.7030508@evision-ventures.com \
    --to=dalecki@evision-ventures.com \
    --cc=acpi-devel@lists.sourceforge.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --cc=torvalds@transmeta.com \
    /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