From: Hans B. <han...@gm...> - 2014-02-06 21:24:29
|
Hi all. I am using a sort of pass-through r/o file system written using the high level API. That is, files on the real file system are massaged before being exposed to the user in a FUSE mount point. Now, something that confuses me is how the page cache works for files accessed through a FUSE file system. Is it the file/inode that is exposed through FUSE that will populate the cache or is it the actual file accessed on the real file system? I would like to flush the page cache in a controlled manner through e.g. fsync(), but can I actually do that from the fs implementation? Or would that have to be done from the process actually opening the file in the FUSE mount point, meaning it is out of my control? Thanks. Hans |