Description of problem: Presently, inode table is protected by mutex which effects glusterfs concurrency. Using rwlock to protect inode would be better,. Version-Release number of selected component (if applicable): How reproducible: Not a bug, no need to reproduce. Steps to Reproduce: 1. 2. 3. A lock usage optimization, not applicable for below items. Actual results: Expected results: Additional info:
REVIEW: https://review.gluster.org/23325 (libglusterfs: use rwlock to protect inode table) posted (#1) for review on master by None
REVIEW: https://review.gluster.org/23681 (inode: reduce inode ref/unref and searching contention) posted (#1) for review on master by Changwei Ge
REVIEW: https://review.gluster.org/23682 (inode: reduce inode ref/unref and searching contention) posted (#1) for review on master by Changwei Ge
REVIEW: https://review.gluster.org/23685 (inode: reduce inode ref/unref and searching contention) posted (#1) for review on master by Changwei Ge
This bug is moved to https://github.com/gluster/glusterfs/issues/1005, and will be tracked there from now on. Visit GitHub issues URL for further details