Hi. On Friday 06 July 2007 17:13:27 Miklos Szeredi wrote: > > To get more serious and practical though, I think the solution is to > > fuzz the userspace/kernelspace distinction. What we really want to > > do is freeze things that submit I/O, then sync, then freeze anything > > that processes I/O and needs to be frozen. In effect, redefine fuse > > processes as freezeable kernel threads. > > 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. No theoretical or practical way?! I'll freely admit to being quite ignorant about fuse, but surely there's some way by which they can be distinguished. Regards, Nigel -- See http://www.tuxonice.net for Howtos, FAQs, mailing lists, wiki and bugzilla info.
Attachment:
pgpuhvSGbRofG.pgp
Description: PGP signature
_______________________________________________ linux-pm mailing list linux-pm@xxxxxxxxxxxxxxxxxxxxxxxxxx https://lists.linux-foundation.org/mailman/listinfo/linux-pm
