[Bugs] [Bug 1664934] glusterfs-fuse client not benefiting from page cache on read after write

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1664934



--- Comment #5 from Manoj Pillai <mpillai at redhat.com> ---
(In reply to Raghavendra G from comment #4)
> From preliminary tests I see two reasons for this:
> 1. inode-invalidations triggered by md-cache
> 2. Fuse auto invalidations

Trying with kernel NFS, another distributed fs solution. I see that cache is
retained at the end of the write test, and both read-after-write and
read-after-read are served from the page cache.

In principle, if kNFS can do it, FUSE should be able to do it. I think :D.

-- 
You are receiving this mail because:
You are on the CC list for the bug.