public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stefan Seyfried <seife@suse.de>
To: Xavier Bestel <xavier.bestel@free.fr>
Cc: nigel@nigel.suspend2.net,
	Jeremy Maitin-Shepard <jmaitins@andrew.cmu.edu>,
	Pavel Machek <pavel@ucw.cz>, Jeremy Maitin-Shepard <jbms@cmu.edu>,
	"Rafael J. Wysocki" <rjw@sisk.pl>,
	linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>
Subject: Re: A kexec approach to hibernation
Date: Tue, 5 Jun 2007 11:34:29 +0200	[thread overview]
Message-ID: <20070605093429.GB5229@suse.de> (raw)
In-Reply-To: <1181031341.6863.164.camel@frg-rhel40-em64t-04>

On Tue, Jun 05, 2007 at 10:15:41AM +0200, Xavier Bestel wrote:
> FWIW, on my old laptop apm beats any kernel solution hands down in terms
> of speed

This might be true on 64MB systems. It is surely not true on multi-Gigabyte-
RAM setups. At least not if you actually use that memory for anything
including filesystem cache.
And you simply cannot buy a new machine today that still supports APM suspend
to disk.
-- 
Stefan Seyfried
QA / R&D Team Mobile Devices        |              "Any ideas, John?"
SUSE LINUX Products GmbH, Nürnberg  | "Well, surrounding them's out." 

This footer brought to you by insane German lawmakers:
SUSE Linux Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)

  reply	other threads:[~2007-06-05  9:35 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-01 20:39 A kexec approach to hibernation Jeremy Maitin-Shepard
2007-06-01 21:39 ` Rafael J. Wysocki
2007-06-01 22:25   ` Jeremy Maitin-Shepard
2007-06-01 23:14     ` Rafael J. Wysocki
2007-06-01 23:54       ` Jeremy Maitin-Shepard
2007-06-02  0:33         ` Rafael J. Wysocki
2007-06-02  1:54           ` Jeremy Maitin-Shepard
2007-06-02  9:22             ` Rafael J. Wysocki
2007-06-04 10:46             ` Pavel Machek
2007-06-04 12:20               ` Matthew Garrett
2007-06-04 13:10                 ` Pavel Machek
2007-06-04 13:16                   ` Matthew Garrett
2007-06-11  2:02                     ` H. Peter Anvin
2007-06-11 22:44                       ` Nigel Cunningham
2007-06-04 22:09               ` Jeremy Maitin-Shepard
2007-06-04 22:36                 ` Nigel Cunningham
2007-06-05  8:15                   ` Xavier Bestel
2007-06-05  9:34                     ` Stefan Seyfried [this message]
2007-06-05  9:40                       ` Xavier Bestel
2007-06-04 22:51                 ` Pavel Machek
2007-06-11 15:07                   ` Jeremy Maitin-Shepard
2007-06-11  3:40             ` Nigel Cunningham
2007-06-11 15:01               ` Jeremy Maitin-Shepard
2007-06-11 15:45                 ` Xavier Bestel
2007-06-11 15:51                   ` Jeremy Maitin-Shepard
2007-06-11 16:03                     ` Xavier Bestel
2007-06-11 17:05                       ` Jeremy Maitin-Shepard
2007-06-04  4:40         ` Vivek Goyal
2007-06-04  5:22           ` Nigel Cunningham
2007-06-04  8:05             ` Rafael J. Wysocki
2007-06-04  8:14               ` Nigel Cunningham
2007-06-04 21:44             ` Jeremy Maitin-Shepard

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=20070605093429.GB5229@suse.de \
    --to=seife@suse.de \
    --cc=jbms@cmu.edu \
    --cc=jmaitins@andrew.cmu.edu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nigel@nigel.suspend2.net \
    --cc=pavel@ucw.cz \
    --cc=rjw@sisk.pl \
    --cc=torvalds@osdl.org \
    --cc=xavier.bestel@free.fr \
    /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