From: Miklos S. <mi...@sz...> - 2007-07-30 12:21:59
|
> That sounds great. In the meantime, I've had the the ->direct_io field > in the fuse_file_info struct pointed out to me. > > It seems that the current perl bindings don't expose this, but if I > modify the Fuse.xs perl XS wrapper to set the flag unconditionally in > open, it appears to allow the original write() size to come through to > my application code. which is great. > > If I understand correctly, setting this field asks fuse to bypass the > page cache, so it would also disable any cacheing of the file contents > (I haven't tested this). That's OK for my application. > > Do you think this would be a workable approach? Or are there > complications and possible problems with this route? One possible complication is that mmap() relies on the page cache, and so it doesn't work with direct_io. Memory mapping is used for example when executing a program or loading a shared library. Miklos |