public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@cyclades.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: "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: Wed, 05 Oct 2005 08:34:33 +1000	[thread overview]
Message-ID: <1128465272.6611.75.camel@localhost> (raw)
In-Reply-To: <20051004205334.GC18481@elf.ucw.cz>

Hi.

On Wed, 2005-10-05 at 06:53, Pavel Machek wrote:
> > > That does not belong to snaphost. The rest is notthat clear, but I have it
> > > working in userspace.
> > 
> > Of course it is doable in the userland, but this does not mean it should be
> > done in the userland.  Personally I don't think so (please see
> > below).
> 
> Even if you don't agree with putting it to userland (and that's
> neccessary -- if we want some features from suspend2), split still
> makes sense.

Not necessary, but desirable in your eyes. I can see that you can make
it work if you're only talking about implementing eye candy, but if
you're serious about adding the substantial improvements from Suspend2
(support for multiple swap partitions, swap files, block sizes != 4096,
asynchronous I/O, readhead where I/O must be synchronous, support for
writing to a network or a generic file (again with block size != 4096)
etc, - let alone support for saving a full image of memory - this is
just going to get uglier and uglier. We can see this already because
you've already dropped swap support, obviously because it's too hard
from userspace.

The tidy up you're proposing is a nice step. But it seems to me to be 
the only good thing and really useful thing to come of this so far.

Pavel, at the PM summit, we agreed to work toward getting Suspend2
merged. I've been working since then on cleaning up the code, splitting
the patches up nicely and so on. In the meantime, you seem to have gone
off on a completely different tangent, going right against what we
agreed then. Can I get you to at least try to come back from that? I'd
be more than willing to help you with cherry picking some changes and
getting them in ahead of the rest of the code. Would you consider
working together to do that? In particular, I'm thinking that I could
send you the refrigerator patches as I have them at the moment, and a
patch to remove the reliance on PageReserved, at least for a start. Any
willingness on your part to give that a try?

Regards,

Nigel
-- 



  reply	other threads:[~2005-10-04 22:35 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 [this message]
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
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=1128465272.6611.75.camel@localhost \
    --to=ncunningham@cyclades.com \
    --cc=akpm@osdl.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    --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