[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <200707051727.36715.rjw@sisk.pl>
Date: Thu, 5 Jul 2007 17:27:35 +0200
From: "Rafael J. Wysocki" <rjw@...k.pl>
To: Matthew Garrett <mjg59@...f.ucam.org>
Cc: Pavel Machek <pavel@....cz>, Paul Mackerras <paulus@...ba.org>,
Alan Stern <stern@...land.harvard.edu>,
Johannes Berg <johannes@...solutions.net>,
Linux-pm mailing list <linux-pm@...ts.linux-foundation.org>,
Kernel development list <linux-kernel@...r.kernel.org>
Subject: Re: removing refrigerator does not help with s2ram vs. fuse deadlocks (was Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway)
On Thursday, 5 July 2007 17:03, Matthew Garrett wrote:
> On Thu, Jul 05, 2007 at 05:04:47PM +0200, Rafael J. Wysocki wrote:
> > On Thursday, 5 July 2007 16:39, Matthew Garrett wrote:
> > > Why?
> >
> > You have processes that don't react to signals, because some other user land
> > task is misbehaving. I'd call that ugly at the very least.
>
> It already happens with, say, NFS. Don't think about it in terms of a
> userland task misbehaving - think of it in terms of a resource becoming
> unavailable.
I think there's a difference between a userland task playing the role of a
resource and a "real" external resource the kernel doesn't control.
IMO, userland tasks should not have the power to affect each other as though
they were parts of the kernel.
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