[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.0707051713440.2753-100000@iolanthe.rowland.org>
Date: Thu, 5 Jul 2007 17:15:24 -0400 (EDT)
From: Alan Stern <stern@...land.harvard.edu>
To: Miklos Szeredi <miklos@...redi.hu>
cc: oliver@...kum.org, <pavel@....cz>, <paulus@...ba.org>,
<johannes@...solutions.net>, <rjw@...k.pl>,
<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 Thu, 5 Jul 2007, Miklos Szeredi wrote:
> I fear, that your efforts to "save" the freezer are in vain. It is
> already moderately hackish with that PF_FREEZER_SKIP and the kernel
> dotted randomly with try_to_freeze() calls, but adding bandaids to try
> to order freezing userspace processes in the right order would just
> make it a horrible mess.
I agree that bandaids won't work. What's needed is something more
radical. Things like FUSE must be written so that the kernel parts
_can_ freeze even while they are waiting for a response from a user
thread.
Alan Stern
-
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