Re: [fuse-devel] tree_lock causes starvation

[bargav y. <by...@ya...>]

----- Original Message ----
> From: Miklos Szeredi <mi...@sz...>
> To: by...@ya...
> Cc: fus...@li...
> Sent: Friday, June 20, 2008 10:16:10 AM
> Subject: Re: [fuse-devel] tree_lock causes starvation
> 
> > we've noticed that when there is steady readdir traffic, for example
> > as generated by multiple find commands, delete operations (rmdir,
> > unlink, rename) seem to get starved out. We're assuming this is due
> > to the rwlock being in a reader-favoring mode. This is the default
> > behaviour of the pthread mutex initialization value chosen by fuse
> > for the lock called "tree_lock". 
> > Is there a specific reason for this decision? What would be the
> > effect of changing the rwlock to prefer writers? 
> 
> Could you try out the CVS version of libfuse?  The "tree_lock" logic
> has been completely rewritten to have much less contention, and better
> fairness on contention.  I'm not sure it's completely fair or not, but
> in practice you shouldn't see any such problems.
> 
> Thanks,
> Miklos

When will this version be released?