public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: William Heimbigner <icxcnika@mar.tar.cc>
To: Pavel Machek <pavel@ucw.cz>
Cc: "John Anthony Kazos Jr." <jakj@j-a-k-j.com>,
	Al Boldi <a1426z@gawab.com>,
	linux-kernel@vger.kernel.org
Subject: Re: Reasons to merge suspend2.
Date: Wed, 25 Apr 2007 16:23:09 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0704251620240.25153@server.thyself> (raw)
In-Reply-To: <20070425161656.GA17253@elf.ucw.cz>

On Wed, 25 Apr 2007, Pavel Machek wrote:

> Hi!
>
>>>> I didn't read your whole post, it's way too long, but I would like to see
>>>> your patch in mainline as an option to swsusp.  What would make this
>>>> infeasible?
>>>
>>> For one thing, Linus said not but yesterday that he doesn't want multiple
>>> competing suspend algorithms like this in the kernel at once. (If I parsed
>>> his message correctly, he doesn't want any in the kernel, but he's putting
>>> up with it because it seems somewhat needed.)
>>
>> Would it be a feasible solution to have a very minimal and generic software
>> suspend in the kernel, and then various userspace implementations could
>> take care of this?
>
> Yes please. If you want suspend-over-nfs or whatever, just add it to
> the userspace; we have enough support in kernel now.
> 									Pavel

That seems like a rather asinine idea to implement. I think you misread my 
question - there are some things that have to be done at the kernel level, such 
as when the entire memory has to be written, but are there portions of the 
existing code, or portions of Suspend2, that could be done in userspace?

If so, you could have a generic suspend mechanism in the kernel, and then 
various other things done in userspace.

William Heimbigner
icxcnika@mar.tar.cc

  reply	other threads:[~2007-04-25 16:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-04-25 12:51 Reasons to merge suspend2 Al Boldi
2007-04-25 15:13 ` John Anthony Kazos Jr.
2007-04-25 16:01   ` William Heimbigner
2007-04-25 16:16     ` Pavel Machek
2007-04-25 16:23       ` William Heimbigner [this message]
2007-04-25 21:33       ` Al Boldi
2007-04-27 20:39   ` Bill Davidsen
  -- strict thread matches above, loose matches on Subject: below --
2007-04-25  1:32 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=Pine.LNX.4.64.0704251620240.25153@server.thyself \
    --to=icxcnika@mar.tar.cc \
    --cc=a1426z@gawab.com \
    --cc=jakj@j-a-k-j.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=pavel@ucw.cz \
    /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