From: Nigel Cunningham <nigel@nigel.suspend2.net>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: nigel@suspend2.net, rjw@sisk.pl, pavel@ucw.cz,
linux-pm@lists.linux-foundation.org, benh@kernel.crashing.org,
linux-kernel@vger.kernel.org, mjg59@srcf.ucam.org,
oliver@neukum.org, paulus@samba.org, mingo@elte.hu
Subject: Re: [RFC][PATCH -mm] PM: Do not sync filesystems from within the freezer
Date: Fri, 6 Jul 2007 17:19:34 +1000 [thread overview]
Message-ID: <200707061719.36054.nigel@nigel.suspend2.net> (raw)
In-Reply-To: <E1I6i0N-0003CY-00@dorka.pomaz.szeredi.hu>
[-- Attachment #1: Type: text/plain, Size: 837 bytes --]
Hi.
On Friday 06 July 2007 17:13:27 Miklos Szeredi wrote:
> > To get more serious and practical though, I think the solution is to
> > fuzz the userspace/kernelspace distinction. What we really want to
> > do is freeze things that submit I/O, then sync, then freeze anything
> > that processes I/O and needs to be frozen. In effect, redefine fuse
> > processes as freezeable kernel threads.
>
> Another myth, that has been debunked already. The problem is: how do
> you define fuse processes? There's no theoretical or even practial
> way to do that.
No theoretical or practical way?! I'll freely admit to being quite ignorant
about fuse, but surely there's some way by which they can be distinguished.
Regards,
Nigel
--
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-06 7:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 14:58 [RFC][PATCH -mm] PM: Do not sync from within the freezer during suspend to RAM Rafael J. Wysocki
2007-07-04 22:48 ` Nigel Cunningham
2007-07-04 22:49 ` Pavel Machek
2007-07-04 22:52 ` Nigel Cunningham
2007-07-05 11:28 ` Rafael J. Wysocki
2007-07-05 11:37 ` Nigel Cunningham
2007-07-05 20:31 ` [RFC][PATCH -mm] PM: Do not sync filesystems from within the freezer Rafael J. Wysocki
2007-07-05 22:00 ` Pavel Machek
2007-07-06 7:02 ` Rafael J. Wysocki
2007-07-06 7:07 ` Nigel Cunningham
2007-07-06 7:13 ` Miklos Szeredi
2007-07-06 7:19 ` Nigel Cunningham [this message]
2007-07-06 7:36 ` Miklos Szeredi
2007-07-07 11:48 ` possible solution for problem 2 (was Re: [RFC][PATCH -mm] PM: Do not sync filesystems from within the freezer) Pavel Machek
2007-07-06 8:59 ` [RFC][PATCH -mm] PM: Do not sync filesystems from within the freezer Benjamin Herrenschmidt
2007-07-06 9:05 ` Miklos Szeredi
2007-07-06 9:13 ` Nigel Cunningham
2007-07-06 9:31 ` Miklos Szeredi
2007-07-06 10:00 ` Rafael J. Wysocki
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=200707061719.36054.nigel@nigel.suspend2.net \
--to=nigel@nigel.suspend2.net \
--cc=benh@kernel.crashing.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.linux-foundation.org \
--cc=miklos@szeredi.hu \
--cc=mingo@elte.hu \
--cc=mjg59@srcf.ucam.org \
--cc=nigel@suspend2.net \
--cc=oliver@neukum.org \
--cc=paulus@samba.org \
--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