path: root/xlators/features/bit-rot/src/bitd/bit-rot.c
diff options
authorNiels de Vos <>2016-08-17 16:44:55 +0200
committerNiels de Vos <>2016-08-25 13:35:43 -0700
commit218c9b033fa44eacbc27d87491abd830548b362e (patch)
tree1e626f0518c86308a6297bb963a23d4bc78cadc0 /xlators/features/bit-rot/src/bitd/bit-rot.c
parent76726da0e86077a8f3a59c02a47fcf2e3994218f (diff)
gfapi: do not cache upcalls if the application is not interested
When the volume option 'features.cache-invalidation' is enabled, upcall events are sent from the brick process to the client. Even if the client is not interested in upcall events itself, md-cache or other xlators may benefit from them. By adding a new 'cache_upcalls' boolean in the 'struct glfs', we can enable the caching of upcalls when the application called glfs_h_poll_upcall(). NFS-Ganesha sets up a thread for handling upcalls in the initialization phase, and calls glfs_h_poll_upcall() before any NFS-client accesses the NFS-export. In the future there will be a more flexible registration API for enabling certain kind of upcall events. Until that is available, this should work just fine. Verificatio of this change is not trivial within our current regression test framework. The bug report contains a description on how to reliably reproduce the problem with the glusterfs-coreutils. Change-Id: I818595c92db50e6e48f7bfe287ee05103a4a30a2 BUG: 1368842 Signed-off-by: Niels de Vos <> Reviewed-on: Smoke: Gluster Build System <> Reviewed-by: Poornima G <> NetBSD-regression: NetBSD Build System <> CentOS-regression: Gluster Build System <> Reviewed-by: soumya k <> Reviewed-by: Kaleb KEITHLEY <>
Diffstat (limited to 'xlators/features/bit-rot/src/bitd/bit-rot.c')
0 files changed, 0 insertions, 0 deletions