[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <E1I5fug-0003ZS-00@dorka.pomaz.szeredi.hu>
Date: Tue, 03 Jul 2007 12:47:18 +0200
From: Miklos Szeredi <miklos@...redi.hu>
To: oliver@...kum.org
CC: linux-pm@...ts.linux-foundation.org, benh@...nel.crashing.org,
nigel@...el.suspend2.net, mjg59@...f.ucam.org,
linux-kernel@...r.kernel.org
Subject: Re: [linux-pm] Re: [PATCH] Remove process freezer from suspend to RAM pathway
> > So to summarize, the plan that makes things work with fuse is:
> >
> > - For STR, don't do the freezer thing.
> >
> > - For STD, don't sys_sync() after you froze
> >
> > There might be -other- issues, but that should get you through some of
>
> At the risk of repeating myself. Character device drivers are written
> with the assumption that normal io and suspend/resume do not race
> with each other due to the freezer.
> What do you intend to do about that?
Oliver, can you please explain your worries in a bit more detail?
I don't claim to know anything about how STR or hibernate works, but
neither seem to have any problem with I/O on the fuse device "racing"
with them.
And conceptually I can't see anything that would cause trouble either.
The fuse kernel module just provides a specialized IPC mechanism,
where one userspace process communicates with another using file
operations and a char dev.
Miklos
-
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