From: Al Boldi <a1426z@gawab.com>
To: Pavel Machek <pavel@ucw.cz>, William Heimbigner <icxcnika@mar.tar.cc>
Cc: "John Anthony Kazos Jr." <jakj@j-a-k-j.com>,
linux-kernel@vger.kernel.org
Subject: Re: Reasons to merge suspend2.
Date: Thu, 26 Apr 2007 00:33:22 +0300 [thread overview]
Message-ID: <200704260033.22378.a1426z@gawab.com> (raw)
In-Reply-To: <20070425161656.GA17253@elf.ucw.cz>
Pavel Machek wrote:
> Hi!
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.
The only way I can think of supporting this, would probably be via an
initramfs trick. But, if you think suspend-over-nfs is possible from
user-space, then why should there be any need for swsusp in the kernel?
Thanks!
--
Al
next prev parent reply other threads:[~2007-04-25 21:31 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-25 12:51 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
2007-04-25 21:33 ` Al Boldi [this message]
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=200704260033.22378.a1426z@gawab.com \
--to=a1426z@gawab.com \
--cc=icxcnika@mar.tar.cc \
--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
all inboxes | Powered by JetHome®