public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Kevin Fenzi <kevin@scrye.com>
From: Kevin Fenzi <kevin@scrye.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Dealing with swsusp vs. pmdisk
Date: Tue, 16 Mar 2004 11:16:09 -0700	[thread overview]
Message-ID: <20040316181612.91F9DB617A@voldemort.scrye.com> (raw)
In-Reply-To: m2d67dr98y.fsf@tnuctip.rychter.com

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

>>>>> "Jan" == Jan Rychter <jan@rychter.com> writes:

>>>>> "Pavel" == Pavel Machek <pavel@ucw.cz> writes:
Jan> [...]  Theodore Ts'o <tytso@mit.edu>:
>>> Pavel, what do you think of the swsusp2 patch, BTW?  My biggest
>>> complaint about it is that since it's maintained outside of the
>>> kernel, it's constantly behind about 0.75 revisions behind the
>>> latest 2.6 release.  The feature set of swsusp2, if they can ever
>>> get it completely bugfree(tm) is certainly impressive.

Pavel> My biggest problem with swsusp2 is that it is big. Also last
Pavel> time I looked it had some ugly hooks sprinkled all over the
Pavel> kernel. Then there are some features I don't like (graphical
Pavel> screens with progress, escape-to-abort) and
Pavel> ithasvariableslikethis. OTOH it supports highmem and smp.

Jan> It also has the advantage of working extremely reliably on 2.4
Jan> (and a large part of the code base is shared, so that's a
Jan> significant data point). I couldn't get it to crash or do
Jan> anything bad for months now, and I'm doing at least several
Jan> suspend/resumes a day on my laptop.

It's been working pretty well on 2.6 for me too. 2.4 was very stable
with it, 2.6 has been less so but is getting there fast. 

Jan> Also, thanks to the excellent compression feature, suspend/resume
Jan> times are very short and in fact competitive with suspend-to-ram
Jan> schemes.

Seconded. With the compression it takes about 15 seconds for my 1gb
memory laptop to suspend and about 15 seconds to resume. This is much
much better than the hardware hibernate my old laptop used to have in
bios. 

Jan> I think it's better not to mix personal preferences (such as the
Jan> escape-to-abort thing) with technical discussions. On a practical
Jan> level, swsusp2 is the only implementation which works reliably,
Jan> does its job very well, and has a responsive maintainer willing
Jan> to fix problems as they arise.

I tried pmdisk and swsusp1 a while back... I couldn't get either to
come back from suspend. swsusp2 is _much_ more reliable for me. 

I would love to see swsusp2 the only implementation in the kernel... 

Just my 2cents. 

Jan> --J.

kevin
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.3 (GNU/Linux)
Comment: Processed by Mailcrypt 3.5.8 <http://mailcrypt.sourceforge.net/>

iD8DBQFAV0Rs3imCezTjY0ERAgEqAKCDe8mNAIywP6kfn8gUqqDRFqvJUQCeIJTr
82Apf+UlCk8jJlxgeTo1WFo=
=62Qn
-----END PGP SIGNATURE-----

  reply	other threads:[~2004-03-16 18:16 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-12 22:46 Dealing with swsusp vs. pmdisk Pavel Machek
2004-03-13  0:47 ` Theodore Ts'o
2004-03-13  2:51   ` Benjamin Herrenschmidt
2004-03-13 12:36     ` Pavel Machek
2004-03-13 22:19       ` Micha Feigin
2004-03-14  0:18       ` Benjamin Herrenschmidt
2004-03-14  0:37         ` Pavel Machek
2004-03-15 20:05           ` Nigel Cunningham
2004-03-16  0:01             ` Benjamin Herrenschmidt
2004-03-15 23:31               ` Nigel Cunningham
2004-03-16  1:40                 ` Benjamin Herrenschmidt
2004-03-15 23:59                   ` Nigel Cunningham
2004-03-16 10:09                   ` Pavel Machek
2004-03-13 12:28   ` Pavel Machek
2004-03-15 23:17     ` Jan Rychter
2004-03-16 18:16       ` Kevin Fenzi, Kevin Fenzi [this message]
2004-03-18 10:21     ` Jan Rychter

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=20040316181612.91F9DB617A@voldemort.scrye.com \
    --to=kevin@scrye.com \
    --cc=linux-kernel@vger.kernel.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