public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: Lorenzo Colitti <lorenzo@colitti.com>
Cc: Nigel Cunningham <ncunningham@cyclades.com>,
	"Rafael J. Wysocki" <rjw@sisk.pl>, Andrew Morton <akpm@osdl.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [swsusp] separate snapshot functionality to separate file
Date: Thu, 6 Oct 2005 00:57:27 +0200	[thread overview]
Message-ID: <20051005225727.GE22781@elf.ucw.cz> (raw)
In-Reply-To: <4344599B.7060308@colitti.com>

On Čt 06-10-05 00:54:19, Lorenzo Colitti wrote:
> Pavel Machek wrote:
> >>- It was dog slow because it doesn't use compression
> >>- Even though it's dog slow, it doesn't save all RAM
> >>  - Therefore the machine is dog slow after resume
> >>- It doesn't have a decent UI
> >>- There is no way to abort suspend once it's started. [...]
> >
> >With uswsusp (aka swsusp3), you can do all this in userland. Stop
> >whining, start hacking... Code is at kernel.org/git/.../linux-sw3.
> 
> But that was exactly my point: there's no need to hack!
> 
> The code is there. It's well tested, fast, stable, and does what users 
> need. It's called suspend2. Why work on yet another implementation 
> instead of just merging that?

Most of that code does not belong it kernel. It can't be "just
merged". If we had nice "vi" implementation in kernel, we'd have to
drop it and start again in userland. This is similar.

								Pavel
-- 
if you have sharp zaurus hardware you don't need... you know my address

  reply	other threads:[~2005-10-05 22:58 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-10-02 23:13 [swsusp] separate snapshot functionality to separate file Pavel Machek
2005-10-03 21:39 ` Rafael J. Wysocki
2005-10-03 23:17   ` Pavel Machek
2005-10-04 15:11     ` Rafael J. Wysocki
2005-10-04 20:53       ` Pavel Machek
2005-10-04 22:34         ` Nigel Cunningham
2005-10-05  8:41           ` Pavel Machek
2005-10-05 21:21             ` Lorenzo Colitti
2005-10-05 22:21               ` Nigel Cunningham
2005-10-05 22:44               ` Pavel Machek
2005-10-05 22:54                 ` Lorenzo Colitti
2005-10-05 22:57                   ` Pavel Machek [this message]
2005-10-05 23:00                     ` Pavel Machek
2005-10-05 23:18                       ` Lorenzo Colitti
2005-10-06 10:10                         ` Alon Bar-Lev
2005-10-06  8:20                           ` Pavel Machek
2005-10-09 23:41                             ` Nigel Cunningham
2005-10-04 22:47         ` Rafael J. Wysocki
2005-10-05  0:06           ` Pavel Machek
2005-10-05  8:20             ` Rafael J. Wysocki
2005-10-05  8:33               ` Pavel Machek
2005-10-06  8:23                 ` Rafael J. Wysocki
2005-10-06 10:42                   ` Pavel Machek
2005-10-06 13:29                     ` Rafael J. Wysocki

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=20051005225727.GE22781@elf.ucw.cz \
    --to=pavel@suse.cz \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lorenzo@colitti.com \
    --cc=ncunningham@cyclades.com \
    --cc=rjw@sisk.pl \
    /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