Joyce Kong ea5207c158 virtio: use one way barrier for split vring used index ... In case VIRTIO_F_ORDER_PLATFORM(36) is not negotiated, then the frontend and backend are assumed to be implemented in software, that is they can run on identical CPUs in an SMP configuration. Thus a weak form of memory barriers like rte_smp_r/wmb, other than rte_cio_r/wmb, is sufficient for this case(vq->hw->weak_barriers == 1) and yields better performance. For the above case, this patch helps yielding even better performance by replacing the two-way barriers with C11 one-way barriers for used index in split ring. Signed-off-by: Joyce Kong <joyce.kong@arm.com> Reviewed-by: Gavin Hu <gavin.hu@arm.com> Reviewed-by: Maxime Coquelin <maxime.coquelin@redhat.com>		2020-05-05 15:54:26 +02:00
..
vhost_kernel_tap.c	net/virtio-user: check tap offload setting failure	2020-01-17 19:46:26 +01:00
vhost_kernel_tap.h	net/virtio-user: do not close tap when disabling queue pairs	2020-01-17 19:46:26 +01:00
vhost_kernel.c	net/virtio-user: do not close tap when disabling queue pairs	2020-01-17 19:46:26 +01:00
vhost_user.c	replace packed attributes	2020-04-16 18:16:46 +02:00
vhost.h	net/virtio: fix build	2019-07-30 19:46:11 +02:00
virtio_user_dev.c	virtio: use one way barrier for split vring used index	2020-05-05 15:54:26 +02:00
virtio_user_dev.h	net/virtio-user: do not close tap when disabling queue pairs	2020-01-17 19:46:26 +01:00