From: Grant G. <gru...@pa...> - 2006-03-16 16:02:59
|
On Mon, Mar 13, 2006 at 12:26:34PM +0100, Miklos Szeredi wrote: > OK. I'm out of ideas, CC-ing parisc-linux, maybe they can help shed > some light on this. Miklos, I took a quick look last week but didn't see anything obvious. I was suspicious of the memcopy() calls to copy stuff to user space. But willy me told those are fine if using the result of kmap() (and then kunmap'ing when done). In a private conversation someone else said they would look at it on the weekend. thanks, grant > > A short summary of the problem: > > (for the full thread see: > http://thread.gmane.org/gmane.comp.file-systems.fuse.devel/2833) > > FUSE doesn't seem to work on PA-RISC (2.6.15 + pa4 patchset) > > The reason appears to be that when the userspace filesystem reads from > the FUSE device, the kernel doesn't copy any data to the userspace > read buffer, though the correct size is returned by read(). > > FUSE uses a combination of get_user_pages(), kmap_atomic() and > memcpy(). After kunmap_atomic(), flush_dcache_page() is called to > avoid virtual aliasing. The data in the read buffer is totally > untouched. > > Can anyone confirm the above behavior of FUSE on PA-RISC? > > Any ideas why this would behave differently on PA-RISC as on other > archs? > > Thanks, > Miklos > _______________________________________________ > parisc-linux mailing list > par...@li... > http://lists.parisc-linux.org/mailman/listinfo/parisc-linux |