[Gluster-devel] Reduce number of inodelk/entrylk calls on ec xlator

[Xavier Hernandez]

On Thursday 03 July 2014 07:40:45 Pranith Kumar Karampuri wrote:
> On 07/01/2014 04:52 PM, Xavier Hernandez wrote:
> > Hi,
> > 
> > current implementation of ec xlator uses inodelk/entrylk before each
> > operation to guarantee exclusive access to the inode. This implementation
> > blocks any other request to the same inode/entry until the previous
> > operation has completed and unlocked it.
> > 
> > This adds a lot of latency to each operation, even if there are no
> > conflicts with other clients. To improve this I was thinking to implement
> > something similar to eager-locking and piggy-backing.
> 
> I think we should make eager-locking, piggy-backing to separate xlators.
> Let me see if we can do that.

Do you mean to create some sort of locks xlator on the client side to 
intercept multiple locks, and automatically grant them if domain, owner and 
user are the same ?