From: "Rafael J. Wysocki" <rjw@sisk.pl>
To: Miklos Szeredi <miklos@szeredi.hu>
Cc: nigel@suspend2.net, benh@kernel.crashing.org, pavel@ucw.cz,
linux-pm@lists.linux-foundation.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 12:00:36 +0200 [thread overview]
Message-ID: <200707061200.37035.rjw@sisk.pl> (raw)
In-Reply-To: <E1I6kA9-0003Zt-00@dorka.pomaz.szeredi.hu>
On Friday, 6 July 2007 11:31, Miklos Szeredi wrote:
> > > > On Fri, 2007-07-06 at 09:13 +0200, Miklos Szeredi wrote:
> > > > >
> > > > > 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.
> > > >
> > > > It could if they told the kernel via some black magic ...
> > > >
> > > > But that still suck. The freezer sucks :-)
> > >
> > > Yeah, and it wouldn't work in practice, since the auxilary tasks might
> > > be part of a library which is not even aware of being used by a "fuse
> > > task".
> >
> > This is why I think the whole concept of filesystems in userspace is broken.
> > Trying to shift things that need special privilege and special handling to
> > userspace is just asking for trouble.
>
> I'm not claiming fuse doesn't introduce problems. I've been tackling
> those problems for a number of years now. Suspend/hibernate is just
> the next thing that needs looking at.
>
> Just blaming either suspend or fuse for these problems is unproductive
> and stupid.
Well, the "stupid" part is a bit offensive, don't you think?
> The problems _are_ solvable if not always simply.
Agreed.
> > You can say it's the kernel code's fault, but then you have to
> > explain why it's only fuse (yeah ok, and XFS) that have problems.
>
> I'm not faulting anythig. My opinion, is that the freezer is not
> needed for suspend, and removing it will not just solve the problems
> with fuse but several others. It probably needs a lot of work, but
> hey, that's why we are here.
>
> The patch posted by Rafael, which lets the freezer skip uninterrupible
> tasks is a step in the right direction.
Thanks.
BTW, I think that this is just less radical than the change proposed by Matthew
and it should address the underlying problems.
Greetings,
Rafael
--
"Premature optimization is the root of all evil." - Donald Knuth
prev parent reply other threads:[~2007-07-06 9:53 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
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 [this message]
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=200707061200.37035.rjw@sisk.pl \
--to=rjw@sisk.pl \
--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 \
/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