public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <ncunningham@clear.net.nz>
To: Patrick Mochel <mochel@osdl.org>
Cc: Linus Torvalds <torvalds@osdl.org>, Pavel Machek <pavel@ucw.cz>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: pm: Revert swsusp to 2.6.0-test3
Date: Tue, 30 Sep 2003 06:49:30 +1200	[thread overview]
Message-ID: <1064861370.2014.4.camel@laptop-linux> (raw)
In-Reply-To: <Pine.LNX.4.44.0309290938010.968-100000@localhost.localdomain>

On Tue, 2003-09-30 at 04:51, Patrick Mochel wrote:
> > Could you also give me some clear direction on where you want me to put
> > my 2.4 port. Should it go in kernel/power, or somewhere else? (I'm
> > assuming you don't want 3 versions of swsusp?!). I'd like to put it in
> > the right place when I start populating swsusp25.bkbits.net, so you're
> > not pulling changesets later that only move the code around (I know bk
> > reduces the cost, but...).
> 
> Please put it in kernel/power/. 

Ok. I'll do that then.

> It's completely alright to have three suspend-to-disk implementations. For 
> one, porting it does not imply that it will be merged into mainline, as 
> is. I would like to see convergence of the competing solutions, and I 
> fully intend to leverage the work that you've done and integrate it into 
> the core power management code, and the pmdisk implementation. 
> 
> The power management core provides, among other things, a framework for 
> properly suspending and resuming a system. Persistant state retention is 
> one aspect, albeit the largest in terms of importance and sheer size. I 
> would like to see backend mechanism for storing state abstracted from the 
> snapshotting process.

I'd certainly like to see such additions somehow implemented as optional
extras. The core functionality ought not be a great monolithic mass.

> This means that there may be several low-level 'drivers' that each deal 
> with reading/writing data on a particular format. And, it means that much 

I've had enquiries about adding support for UML, NFS and encryption
support; they would match well with your desire for a more general
solution. 

> of the overhead of swsusp, etc, can be folded into the core PM code. 

Yes; I have a pretty clear distinction between the code for freezing
processes and syncing data and that which actually saves the data.

> I do not have more technical details about this ATM, but I will work with 
> you to make sure things are streamlined as much as possible during and 
> after your port.

Great. I'll start the work in earnest tomorrow. Today I'm packing up
books :>

Nigel

-- 
Nigel Cunningham
495 St Georges Road South, Hastings 4201, New Zealand

You see, at just the right time, when we were still powerless,
Christ died for the ungodly.
	-- Romans 5:6, NIV.


      reply	other threads:[~2003-09-29 18:55 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-28 12:05 pm: Revert swsusp to 2.6.0-test3 pavel
2003-09-28 17:40 ` Linus Torvalds
2003-09-28 17:58   ` Pavel Machek
2003-09-28 20:24     ` Pavel Machek
2003-09-29 16:13     ` Patrick Mochel
2003-09-29 19:24       ` Pavel Machek
2003-09-29 20:46     ` Pavel Machek
2003-09-29 21:34       ` Pavel Machek
2003-09-29 21:59         ` Pavel Machek
2003-09-30  0:43       ` Andreas Jellinghaus
2003-09-30  0:48         ` Patrick Mochel
2003-09-30  1:16           ` Mark W. Alexander
2003-09-28 18:48   ` Nigel Cunningham
2003-09-28 19:06     ` Pavel Machek
2003-09-29 16:51     ` Patrick Mochel
2003-09-29 18:49       ` Nigel Cunningham [this message]

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=1064861370.2014.4.camel@laptop-linux \
    --to=ncunningham@clear.net.nz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mochel@osdl.org \
    --cc=pavel@ucw.cz \
    --cc=torvalds@osdl.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