Bug 2006631

Summary: Perf: mem_acct: Make mem_accounting lock free
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Mohit Agrawal <moagrawa>
Component: coreAssignee: Mohit Agrawal <moagrawa>
Status: CLOSED ERRATA QA Contact: Vivek Das <vdas>
Severity: urgent Docs Contact:
Priority: urgent    
Version: rhgs-3.5CC: nyancey, rhs-bugs, sajmoham, sasundar, sheggodu, tshacked, vdas, ykaul
Target Milestone: ---Keywords: Improvement, Performance, ZStream
Target Release: RHGS 3.5.z Batch Update 7   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: glusterfs-6.0-62 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-31 12:37:31 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 Mohit Agrawal 2021-09-22 05:00:48 UTC
The _gf(c|m)alloc and __gf_free memory allocation api calls gf_mem_set_acct_info function to save memory accounting on xlator and to update the record it takes lock.During testing we have observed the mem_acct mutex has contention.

Solution: To avoid contention make it lock free and the performance data is available at github issue #2771(https://github.com/gluster/glusterfs/issues/2771)

Comment 1 Mohit Agrawal 2021-09-22 05:02:34 UTC
The upstream patch is to resolve the same
https://github.com/gluster/glusterfs/pull/2797

Comment 7 Yaniv Kaul 2021-11-09 12:05:24 UTC
Can we get a QE ack on this?

Comment 23 errata-xmlrpc 2022-05-31 12:37:31 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (glusterfs bug fix update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:4840