[Gluster-devel] disabling caching and other optimizations for internal fops

Raghavendra Bhat rabhat at redhat.com
Tue Aug 27 07:12:16 UTC 2013


Hi,

As of now, the performance xlators cache the data and perform some 
optimizations for all the fops irrespective of whether the fop is 
generated from the application or internal xlator. I think, performance 
xlators should come in to picture for only the fops generated by the 
applications. Imagine the situation where a graph change happens and 
fuse xlator sends open call on the fds to migrate them to the new graph. 
But the open call might not reach posix if open-behind unwinds success 
to fuse xlator.

It can be done in 2 ways.

1) Set a key in dictionary if the call is generated internally
OR
2) Set a flag in the callstack itself, whether the fop is internal fop 
or generated from the application.

Please provide feedback.


Regards,
Raghavendra Bhat




More information about the Gluster-devel mailing list