Bug 1746368

Summary:	Use rwlock to protect inode table
Product:	[Community] GlusterFS	Reporter:	Changwei Ge <gechangwei>
Component:	locks	Assignee:	bugs <bugs>
Status:	CLOSED UPSTREAM	QA Contact:
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	mainline	CC:	bugs
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-03-12 13:23:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Changwei Ge 2019-08-28 09:48:31 UTC

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:

Comment 1 Worker Ant 2019-08-29 04:11:44 UTC

REVIEW: https://review.gluster.org/23325 (libglusterfs: use rwlock to protect inode table) posted (#1) for review on master by None

Comment 2 Worker Ant 2019-11-06 14:14:21 UTC

REVIEW: https://review.gluster.org/23681 (inode: reduce inode ref/unref and searching contention) posted (#1) for review on master by Changwei Ge

Comment 3 Worker Ant 2019-11-07 02:24:40 UTC

REVIEW: https://review.gluster.org/23682 (inode: reduce inode ref/unref and searching contention) posted (#1) for review on master by Changwei Ge

Comment 4 Worker Ant 2019-11-07 03:06:40 UTC

REVIEW: https://review.gluster.org/23685 (inode: reduce inode ref/unref and searching contention) posted (#1) for review on master by Changwei Ge

Comment 5 Worker Ant 2020-03-12 13:23:07 UTC

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