From: Ducrot Bruno <ducrot@poupinou.org>
To: Nigel Cunningham <ncunningham@clear.net.nz>
Cc: Pavel Machek <pavel@ucw.cz>,
"Grover, Andrew" <andrew.grover@intel.com>,
ducrot@poupinou.org,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
ACPI List <acpi-devel@lists.sourceforge.net>
Subject: Re: [ACPI] Re: [PATCH] s4bios for 2.5.59 + apci-20030123
Date: Thu, 6 Feb 2003 11:16:45 +0100 [thread overview]
Message-ID: <20030206101645.GO1205@poup.poupinou.org> (raw)
In-Reply-To: <1044477704.1648.19.camel@laptop-linux.cunninghams>
On Thu, Feb 06, 2003 at 09:41:44AM +1300, Nigel Cunningham wrote:
> On Wed, 2003-02-05 at 11:10, Pavel Machek wrote:
> > Some people apparently want slower suspend/resume but have all caches
> > intact when resumed. Thats not easy for swsusp but they can have that
> > with S4bios. And S4bios is usefull for testing device support; it
> > seems to behave slightly differently to S3 meaning better testing.
>
> Whether its slower depends on the hardware; on my 128MB Celeron 933
> laptop (17MB/s HDD), I can write an image of about 120MB, reboot and get
> back up and running in around a minute and a half. That's about the same
> as far as I remember, but has (as you say) the advantage of not still
> having to get things swapped back in.
The problem is the speed of the suspending process, not the whole suspend/resume
sequence, especially in case of emergency suspending due to thermal condition,
etc.
--
Ducrot Bruno
-- Which is worse: ignorance or apathy?
-- Don't know. Don't care.
next prev parent reply other threads:[~2003-02-06 10:07 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-04 1:25 [PATCH] s4bios for 2.5.59 + apci-20030123 Grover, Andrew
2003-02-04 22:10 ` Pavel Machek
2003-02-05 20:05 ` [ACPI] " Ducrot Bruno
2003-02-05 20:41 ` Nigel Cunningham
2003-02-06 10:16 ` Ducrot Bruno [this message]
2003-02-06 19:41 ` Nigel Cunningham
2003-02-06 21:05 ` Ducrot Bruno
2003-02-07 3:57 ` Nigel Cunningham
2003-02-07 16:00 ` Pavel Machek
2003-02-09 19:42 ` Nigel Cunningham
2003-02-06 15:37 ` Pavel Machek
2003-02-06 19:44 ` Nigel Cunningham
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=20030206101645.GO1205@poup.poupinou.org \
--to=ducrot@poupinou.org \
--cc=acpi-devel@lists.sourceforge.net \
--cc=andrew.grover@intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=ncunningham@clear.net.nz \
--cc=pavel@ucw.cz \
/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;
as well as URLs for NNTP newsgroup(s).