|
From: | Anand Avati |
Subject: | Re: [Gluster-devel] disabling caching and other optimizations for internal fops |
Date: | Tue, 27 Aug 2013 21:50:51 -0700 |
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
_______________________________________________
Gluster-devel mailing list
address@hidden
https://lists.nongnu.org/mailman/listinfo/gluster-devel
[Prev in Thread] | Current Thread | [Next in Thread] |