Bug 1678991 - Granular lock to reduce lock contention at io-thread
Summary: Granular lock to reduce lock contention at io-thread
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: GlusterFS
Classification: Community
Component: io-threads
Version: mainline
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
Assignee: Mohit Agrawal
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-02-20 04:46 UTC by Mohit Agrawal
Modified: 2020-03-12 14:48 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2020-03-12 14:48:16 UTC
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Gluster.org Gerrit 21039 0 None Abandoned iothread: Use the granular lock to reduce lock contention 2019-09-11 19:30:35 UTC

Description Mohit Agrawal 2019-02-20 04:46:39 UTC 
Description of problem:
The current code of io-thread xlator to execute fop is not granular so in case of brick multiplex performance is reduced.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Worker Ant 2019-02-20 04:51:08 UTC 
REVIEW: https://review.gluster.org/21039 (iothread: Use the granular lock to reduce lock contention) posted (#33) for review on master by MOHIT AGRAWAL
Comment 2 Worker Ant 2020-03-12 14:48:16 UTC 
This bug is moved to https://github.com/gluster/glusterfs/issues/1064, and will be tracked there from now on. Visit GitHub issues URL for further details
Note You need to log in before you can comment on or make changes to this bug.