vppinfra: refactor use of CLIB_MEMORY_BARRIER () 57/20857/3
authorjaszha03 <jason.zhang2@arm.com>
Wed, 12 Jun 2019 21:01:19 +0000 (16:01 -0500)
committerDave Barach <openvpp@barachs.net>
Tue, 30 Jul 2019 16:22:03 +0000 (16:22 +0000)
commitf25e7cfa5c615e1972d5823b65ca579f951d68a5
tree47c4e91b45710d861081d1933e2e8cbe3f56fe42
parent6b03ab73116a7746f9480ea00c3924dcecb2799f
vppinfra: refactor use of CLIB_MEMORY_BARRIER ()

All instances of test_and_set locks used the following sequence
to release the locks:

CLIB_MEMORY_BARRIER ();
p->lock = 0; // p is a generic struct with a TAS lock

Use clib_atomic_release to generate more efficient assembly code.

Type: refactor

Change-Id: Idca3a38b1cf43578108bdd1afe83b6ebc17a4c68
Signed-off-by: Jason Zhang <jason.zhang2@arm.com>
Reviewed-by: Honnappa Nagarahalli <honnappa.nagarahalli@arm.com>
Reviewed-by: Lijian Zhang <Lijian.Zhang@arm.com>
src/plugins/map/map.h
src/svm/ssvm.h
src/vnet/classify/vnet_classify.c
src/vnet/dns/dns.h
src/vppinfra/elog.c
src/vppinfra/lock.h
src/vppinfra/mheap.c