From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: rjw@sisk.pl, a1426z@gawab.com, jeremy@goop.org, jbms@cmu.edu,
pavel@ucw.cz, nickpiggin@yahoo.com.au,
linux-kernel@vger.kernel.org, akpm@linux-foundation.org
Subject: Re: Hibernation Redesign
Date: Wed, 11 Jul 2007 22:46:50 +1000 [thread overview]
Message-ID: <200707112246.54510.nigel@nigel.suspend2.net> (raw)
In-Reply-To: <E1I8bEi-0000HF-00@dorka.pomaz.szeredi.hu>
[-- Attachment #1: Type: text/plain, Size: 2284 bytes --]
Hi.
On Wednesday 11 July 2007 22:24:04 Miklos Szeredi wrote:
> > No other _proper_ solutions have been proposed. Everyone who suggests
removing
> > the freezer also suggests implementing it all over again. It might be
sending
> > SIGSTOP to everything. It might be shifting the desk chairs around and
> > creating a completely new kernel context, but they always have the same
> > goal - stopping the existing activity, and they all come with their own
> > issues (even if they're not obvious yet because the alternatives are
> > currently vapourware to one extent or another).
>
> Hey, I know precious little about drivers and power management, but I
> can clarly see, that
>
> a) stopping all tasks and requiring them to finish any syscall they
> are in
>
> b) stopping tasks _in the driver_ that are trying to access the
> harware during/after suspend
>
> are completely different solutions, the later being much more fine
> grained and not having all of the mentioned problems that the former
> exhibits.
The point to freezing tasks isn't just to stop drivers doing work. It's also
to stop userspace doing work and thereby increase reliability. The more work
that is occuring while we're trying to write a hibernation image, the less
reliable the hibernation will be (competing for memory and so on) and the
slower it will be (competing for cycles etc).
> > IMHO, the real solution is to go back to the original issue and fix it
> > properly. Make fuse filesystems play nicely with the existing freezer.
I've
> > just gone back and looked at the point where you started talking
> > about "malicious filesystems". You talk about fuse imposing certain
ordering
> > in the userspace tasks being frozen. Please, say more. What ordering
issues?
> > Why? How can such ordering be determined programmatically?
>
> It can't. If you are interested, please read through that thread. If
> something's still not clear, let's discuss it further.
You can say it "imposes certain ordering" but you can say what that ordering
is?! How about mount order? That must be a good start.
Regards,
Nigel (off to bed now).
--
See http://www.tuxonice.net for Howtos, FAQs, mailing
lists, wiki and bugzilla info.
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2007-07-11 12:46 UTC|newest]
Thread overview: 60+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-08 14:37 Hibernation Redesign (was: malicious filesystems (was Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM) Al Boldi
2007-07-09 4:11 ` Hibernation Redesign Jeremy Maitin-Shepard
2007-07-09 4:29 ` Nick Piggin
2007-07-09 4:36 ` Jeremy Maitin-Shepard
2007-07-09 4:45 ` Nick Piggin
2007-07-09 4:54 ` Jeremy Maitin-Shepard
2007-07-09 4:58 ` Nick Piggin
2007-07-09 5:33 ` Nick Piggin
2007-07-09 6:22 ` Jeremy Fitzhardinge
2007-07-09 13:45 ` Pavel Machek
2007-07-09 14:02 ` Oliver Neukum
2007-07-09 14:26 ` Jeremy Maitin-Shepard
2007-07-09 15:09 ` Oliver Neukum
2007-07-09 15:27 ` Jeremy Maitin-Shepard
2007-07-09 4:39 ` Nick Piggin
2007-07-09 13:52 ` Pavel Machek
2007-07-09 15:30 ` Al Boldi
2007-07-10 1:29 ` Nick Piggin
2007-07-10 2:28 ` Jeremy Maitin-Shepard
2007-07-10 14:57 ` Jeremy Fitzhardinge
2007-07-10 17:25 ` Jeremy Maitin-Shepard
2007-07-10 22:59 ` Jeremy Fitzhardinge
2007-07-11 4:11 ` Al Boldi
2007-07-11 10:27 ` Rafael J. Wysocki
2007-07-11 10:42 ` Miklos Szeredi
2007-07-11 11:04 ` Rafael J. Wysocki
2007-07-11 11:11 ` Miklos Szeredi
2007-07-11 11:50 ` Rafael J. Wysocki
2007-07-11 11:54 ` Miklos Szeredi
2007-07-11 12:00 ` Nigel Cunningham
2007-07-11 12:09 ` Miklos Szeredi
2007-07-11 12:17 ` Nigel Cunningham
2007-07-11 12:27 ` Rafael J. Wysocki
2007-07-11 12:29 ` Miklos Szeredi
2007-07-11 21:04 ` Rafael J. Wysocki
2007-07-12 9:15 ` Pavel Machek
2007-07-12 22:13 ` Miklos Szeredi
2007-07-11 12:19 ` Rafael J. Wysocki
2007-07-11 12:49 ` Nigel Cunningham
2007-07-11 21:06 ` Rafael J. Wysocki
2007-07-11 12:11 ` Nigel Cunningham
2007-07-11 12:24 ` Miklos Szeredi
2007-07-11 12:46 ` Nigel Cunningham [this message]
2007-07-11 12:55 ` Miklos Szeredi
2007-07-11 13:16 ` Jeremy Maitin-Shepard
2007-07-11 20:48 ` Mark Lord
2007-07-11 21:14 ` Rafael J. Wysocki
2007-07-11 22:17 ` Al Boldi
2007-07-11 22:34 ` Rafael J. Wysocki
2007-07-11 23:12 ` Al Boldi
2007-07-11 23:31 ` Nigel Cunningham
2007-07-12 3:11 ` Al Boldi
2007-07-12 13:20 ` Rafael J. Wysocki
2007-07-16 6:04 ` Nick Piggin
2007-07-12 20:29 ` Jeremy Maitin-Shepard
2007-07-11 23:46 ` Nigel Cunningham
2007-07-11 17:55 ` david
2007-07-11 22:54 ` Nigel Cunningham
2007-07-10 17:45 ` Al Boldi
2007-07-10 18:20 ` Jeremy Maitin-Shepard
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=200707112246.54510.nigel@nigel.suspend2.net \
--to=nigel@nigel.suspend2.net \
--cc=a1426z@gawab.com \
--cc=akpm@linux-foundation.org \
--cc=jbms@cmu.edu \
--cc=jeremy@goop.org \
--cc=linux-kernel@vger.kernel.org \
--cc=miklos@szeredi.hu \
--cc=nickpiggin@yahoo.com.au \
--cc=nigel@suspend2.net \
--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