diff options
| author | Mohit Agrawal <moagrawal@redhat.com> | 2018-09-19 14:32:22 +0530 |
|---|---|---|
| committer | Atin Mukherjee <amukherj@redhat.com> | 2018-09-20 03:46:05 +0000 |
| commit | 4f6ae853ffa9d06446407f389aaef61ac0b3b424 (patch) | |
| tree | c96cf2566835a9c8513a073a94f83e2d1a5ba8fa /xlators/mgmt/glusterd/src/glusterd.c | |
| parent | 6a49bce014ac546582cf2409fd9933115406c808 (diff) | |
glusterd: Use GF_ATOMIC to update 'blockers' counter at glusterd_conf
Problem:
Currently in glusterd code uses sync_lock/sync_unlock to update blockers
counter which could add delays to the overall transaction phase
escpecially when there's a batch of volume stop operations processed by
glusterd in brick multiplexing mode.
Solution: Use GF_ATOMIC to update blocker counter to ensure unnecessary
context switching can be avoided.
Change-Id: Ie13177dfee2af66687ae7cf5c67405c152853990
Fixes: bz#1631128
Signed-off-by: Mohit Agrawal <moagrawal@redhat.com>
Diffstat (limited to 'xlators/mgmt/glusterd/src/glusterd.c')
| -rw-r--r-- | xlators/mgmt/glusterd/src/glusterd.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/xlators/mgmt/glusterd/src/glusterd.c b/xlators/mgmt/glusterd/src/glusterd.c index 187038fc029..3da579464bb 100644 --- a/xlators/mgmt/glusterd/src/glusterd.c +++ b/xlators/mgmt/glusterd/src/glusterd.c @@ -1976,7 +1976,7 @@ init(xlator_t *this) } } - conf->blockers = 0; + GF_ATOMIC_INIT(conf->blockers, 0); /* If the peer count is less than 2 then this would be the best time to * spawn process/bricks that may need (re)starting since last time * (this) glusterd was up. */ |