On Sun, Jan 30, 2005 at 01:40:35PM +0100, Miklos Szeredi wrote: > > the kernel-part of fuse tells any kernel-level callers to > > "go away, come back later". > > > > obviously this gives time for the kernel-part to "wake up" the > > userspace daemon, obtain an answer, such that when the kernel-level > > caller _does_ come back, the information is available. > > It doesn't do that and never did. ERESTARTSYS is only returned if the > operation is interrupted, and in that case the operation is restarted > from scratch, the answer to the old request is never used. oh??
*confused* - well that's good, then! glad that's cleared up! [must contact you again about this when i have time] > > in a nutshell, inodes is an optimisation from a unix > > perspective: by providing an inode based interface, you are > > burdening _all_ filesystem implementers with that concept. > > Yes. However I think the burden on performance (nothing else), is > justified by the better flexibility. i understand. l. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/