public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Nigel Cunningham <nigel@suspend2.net>
To: "Rafael J. Wysocki" <rjw@sisk.pl>
Cc: Jens Axboe <axboe@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: [Suspend2][ 0/9] Extents support.
Date: Wed, 28 Jun 2006 09:47:55 +1000	[thread overview]
Message-ID: <200606280947.58916.nigel@suspend2.net> (raw)
In-Reply-To: <200606280019.32045.rjw@sisk.pl>

[-- Attachment #1: Type: text/plain, Size: 2292 bytes --]

Hi.

On Wednesday 28 June 2006 08:19, Rafael J. Wysocki wrote:
> Hi,
>
> On Tuesday 27 June 2006 11:35, Nigel Cunningham wrote:
> > On Tuesday 27 June 2006 19:26, Rafael J. Wysocki wrote:
> > > > > Now I haven't followed the suspend2 vs swsusp debate very closely,
> > > > > but it seems to me that your biggest problem with getting this
> > > > > merged is getting consensus on where exactly this is going. Nobody
> > > > > wants two different suspend modules in the kernel. So there are two
> > > > > options - suspend2 is deemed the way to go, and it gets merged and
> > > > > replaces swsusp. Or the other way around - people like swsusp more,
> > > > > and you are doomed to maintain suspend2 outside the tree.
> > > >
> > > > Generally, I agree, although my understanding of Rafael and Pavel's
> > > > mindset is that swsusp is a dead dog and uswsusp is the way they want
> > > > to see things go. swsusp is only staying for backwards compatability.
> > > > If that's the case, perhaps we can just replace swsusp with Suspend2
> > > > and let them have their existing interface for uswsusp. Still not
> > > > ideal, I agree, but it would be progress.
> > >
> > > Well, ususpend needs some core functionality to be provided by the
> > > kernel, like freezing/thawing processes (this is also used by the STR),
> > > snapshotting the system memory.  These should be shared with the
> > > in-kernel suspend, be it swsusp or suspend2.
> >
> > If I modify suspend2 so that from now on it replaces swsusp, using
> > noresume, resume= and echo disk > /sys/power/state in a way that's
> > backward compatible with swsusp and doesn't interfere with uswsusp
> > support, would you be happy? IIRC, Pavel has said in the past he wishes
> > I'd just do that, but he's not you of course.
>
> That depends on how it's done.  For sure, I wouldn't like it to be done in
> the "everything at once" manner.

I'm not sure I get what you're saying. Do you mean you'd prefer them to 
coexist for a time in mainline? If so, I'd point out that suspend2 uses 
different parameters at the moment precisely so they can coexist, so that 
wouldn't be any change.

Regards,

Nigel
-- 
See http://www.suspend2.net for Howtos, FAQs, mailing
lists, wiki and bugzilla info.

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2006-06-27 23:48 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-26 16:54 [Suspend2][ 0/9] Extents support Nigel Cunningham
2006-06-26 16:54 ` [Suspend2][ 1/9] [Suspend2] Extents header Nigel Cunningham
2006-06-26 16:54 ` [Suspend2][ 2/9] [Suspend2] Extent allocation routines Nigel Cunningham
2006-06-26 16:54 ` [Suspend2][ 3/9] [Suspend2] Free a whole extent chain Nigel Cunningham
2006-06-26 16:54 ` [Suspend2][ 4/9] [Suspend2] Add extent to " Nigel Cunningham
2006-06-26 16:54 ` [Suspend2][ 5/9] [Suspend2] Serialise extent chains Nigel Cunningham
2006-06-26 16:54 ` [Suspend2][ 6/9] [Suspend2] Get next extent in an extent state Nigel Cunningham
2006-06-26 16:54 ` [Suspend2][ 7/9] [Suspend2] Extent state to the start Nigel Cunningham
2006-06-26 16:54 ` [Suspend2][ 8/9] [Suspend2] Extent state save and restore Nigel Cunningham
2006-06-26 16:54 ` [Suspend2][ 9/9] [Suspend2] Extent header Nigel Cunningham
2006-06-26 21:20 ` [Suspend2][ 0/9] Extents support Rafael J. Wysocki
2006-06-27  4:28   ` Nigel Cunningham
2006-06-27  5:36     ` Jens Axboe
2006-06-27  5:39       ` Nigel Cunningham
2006-06-27  7:05         ` Jens Axboe
2006-06-27  7:39           ` Nigel Cunningham
2006-06-27  7:59             ` Jens Axboe
2006-06-27  8:12               ` Greg KH
2006-06-27  8:22                 ` Jens Axboe
2006-06-27  8:58                 ` Nigel Cunningham
2006-06-28 21:11                   ` Pavel Machek
2006-06-28 22:25                     ` Nigel Cunningham
2006-06-28 22:44                       ` Pavel Machek
2006-06-28 23:14                         ` Nigel Cunningham
2006-06-30 17:36                           ` Pavel Machek
2006-06-29  3:11                       ` Martin J. Bligh
2006-06-27  9:07               ` Nigel Cunningham
2006-06-27  9:26                 ` Rafael J. Wysocki
2006-06-27  9:35                   ` Nigel Cunningham
2006-06-27 22:19                     ` Rafael J. Wysocki
2006-06-27 23:47                       ` Nigel Cunningham [this message]
2006-06-28 22:35                         ` Rafael J. Wysocki
2006-06-28 23:26                           ` Nigel Cunningham
2006-06-29 20:52                             ` Rafael J. Wysocki
2006-06-30 17:58                           ` Pavel Machek
2006-06-28 11:28             ` Rahul Karnik
2006-06-28 12:42               ` Nigel Cunningham
2006-06-28 14:42                 ` Pekka Enberg
2006-06-28 23:37                   ` Nigel Cunningham
2006-06-29  5:19                     ` Pekka Enberg
2006-06-29  5:44                       ` Nigel Cunningham
2006-06-29 21:11                         ` Rafael J. Wysocki
2006-06-30 17:55                     ` suspend2 merge [was Re: [Suspend2][ 0/9] Extents support.] Pavel Machek
2006-07-01  9:31                       ` Dumitru Ciobarcianu
2006-06-28 22:41                 ` [Suspend2][ 0/9] Extents support Rafael J. Wysocki
2006-06-28 14:37               ` Olivier Galibert
2006-06-28 21:05                 ` Pavel Machek
2006-06-27  7:06         ` Greg KH
2006-06-27  7:27           ` Nigel Cunningham
2006-06-27  7:53             ` Greg KH
2006-06-27  9:08               ` Nigel Cunningham

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=200606280947.58916.nigel@suspend2.net \
    --to=nigel@suspend2.net \
    --cc=axboe@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --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