[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200707051614.19300.rjw@sisk.pl>
Date: Thu, 5 Jul 2007 16:14:17 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Miklos Szeredi <miklos@...redi.hu>
Cc: pavel@....cz, oliver@...kum.org, paulus@...ba.org,
stern@...land.harvard.edu, johannes@...solutions.net,
linux-pm@...ts.linux-foundation.org, linux-kernel@...r.kernel.org,
mjg59@...f.ucam.org, benh@...nel.crashing.org
Subject: Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway
On Thursday, 5 July 2007 15:50, Miklos Szeredi wrote:
> > > > Don't you think, however, that it can be modified a little to play well,
> > > > for example, with the freezer?
> > >
> > > I could stick a couple of try_to_freeze()s into fuse, and that would
> > > make suspend failure less likely. But making problems less easy to
> > > reproduce is not a good thing.
> >
> > So, how about eliminating them?
>
> That can't be done just within fuse, a process might be sleeping on a
> VFS mutex. Do we want to hack VFS as well?
No.
> I guess I know your answer. But it ain't gonna work. Suspend code
> really doesn't belong in VFS, and I'm pretty sure the maintainers of
> that little piece of code would agree with me on this.
Surprise, surprise. Not that I'm scared of the VFS maintainers, though. ;-)
Greetings,
Rafael
--
"Premature optimization is the root of all evil." - Donald Knuth
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists