Several sets of numbers have been published in lkml on this.
I will work on sending out my updates to the vfs locking document
you wrote ASAP. AFAICS, most dcache APIs work as is despite lockfree
lookup. As long as we follow those rules, we should be ok.
> Note that for vfsmounts proposed RCU patch had been utterly useless -
> practically all improvements had been from separate lock for vfsmounts
> (see akpm tree).
Yes and that is why Maneesh's patch had two parts. In that case benefit
came from reducing acquisition of dcache_lock by the first part itself -
using a separate lock for vfsmounts. It does not seem possible to
split up dcache_lock any further without very significant changes in vfs.
The acquisition of vfsmount_lock by itself was not significant enough
to really warrant lockfree lookup.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/