From: Nigel Cunningham <ncunningham@crca.org.au>
To: Maxim Levitsky <maximlevitsky@gmail.com>
Cc: "Rafael J. Wysocki" <rjw@sisk.pl>,
pm list <linux-pm@lists.linux-foundation.org>,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>,
Linus Torvalds <torvalds@linux-foundation.org>,
LKML <linux-kernel@vger.kernel.org>
Subject: Re: [linux-pm] [RFC] Asynchronous suspend/resume - test results
Date: Tue, 22 Dec 2009 07:04:28 +1100 [thread overview]
Message-ID: <4B2FD4CC.5070609@crca.org.au> (raw)
In-Reply-To: <1261425499.4328.10.camel@maxim-laptop>
Hi.
Maxim Levitsky wrote:
> On Mon, 2009-12-21 at 18:25 +1100, Nigel Cunningham wrote:
>> Hi.
>>
>> Rafael J. Wysocki wrote:
>>> I'm not sure what the next step should be at this point. To me, the picture is
>>> quite clear now, but perhaps we ought to run more tests on some other machines
>>> or something. Please let me know what you think.
>> Looks great. If you do decide you want other machines tested, I'll
>> happily try the machines around here:
>>
>> - Dell M1530
>> - Omnibook XE3-GF.
>> - Via LN10000 based Mythtv Box
>> - Desktop machine - Some Intel-based mobo I've forgotten the name of.
>>
>> I've been quietly following the thread, but have lost track of what
>> iteration of the patch you're on, so if you'd give me a pointer to it,
>> I'd be grateful.
>>
>> By the way, I haven't forgotten about sending some real patches for
>> swsusp (ie more than just cleanups). I'm just busy with other things and
>> also thinking carefully about what order to do things in.
>
> I vote for ability to save all ram to the disk.
> After several days of testing I managed to make my system do s2disk
> really reliable (~300 cycles tested), but suspending when memory is
> tight still fails sometimes.
>
> I didn't yet use your tuxonice system though.
Well, I want to and intend on working towards merging as much of
TuxOnIce as people will allow in, but it will take a long time because
there are so many modifications to do, I don't have that much time to
work on it, am splitting the time I do have and am still have a couple
of new features I want to do to TuxOnIce.
Regards,
Nigel
next prev parent reply other threads:[~2009-12-21 20:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 0:40 [RFC] Asynchronous suspend/resume - test results Rafael J. Wysocki
2009-12-21 7:25 ` [linux-pm] " Nigel Cunningham
2009-12-21 7:35 ` Dmitry Torokhov
2009-12-21 19:58 ` Maxim Levitsky
2009-12-21 20:04 ` Nigel Cunningham [this message]
2009-12-23 20:46 ` Rafael J. Wysocki
2009-12-24 2:32 ` Nigel Cunningham
2009-12-24 22:10 ` Rafael J. Wysocki
2009-12-25 20:57 ` Nigel Cunningham
2009-12-26 21:33 ` Rafael J. Wysocki
2009-12-26 22:03 ` Nigel Cunningham
2009-12-27 14:20 ` Rafael J. Wysocki
2009-12-21 20:10 ` Alan Stern
2009-12-21 20:36 ` Rafael J. Wysocki
2009-12-21 20:54 ` Alan Stern
2009-12-21 23:00 ` Linus Torvalds
2009-12-23 20:35 ` Rafael J. Wysocki
2010-01-02 21:28 ` [Update] " Rafael J. Wysocki
2010-01-04 17:17 ` Jesse Barnes
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=4B2FD4CC.5070609@crca.org.au \
--to=ncunningham@crca.org.au \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=maximlevitsky@gmail.com \
--cc=rjw@sisk.pl \
--cc=torvalds@linux-foundation.org \
/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