[dpdk-dev] [PATCH] vhost: call write barrier before used index update

2015-10-21 Thread Nikita Kalyazin
Hi, > This has been discussed a number of times before on list, and the consensus > seems to be that the correct way to fix this is to introduce a set of specific > barrier operations that insert the correct barrier type on each architecture, > i.e. compiler barriers on IA, and full wmbs on archit

[dpdk-dev] [PATCH] vhost: call write barrier before used index update

2015-10-21 Thread Bruce Richardson
On 21/10/2015 16:42, Nikita Kalyazin wrote: > Hi, > >> This has been discussed a number of times before on list, and the consensus >> seems to be that the correct way to fix this is to introduce a set of >> specific >> barrier operations that insert the correct barrier type on each architecture,

[dpdk-dev] [PATCH] vhost: call write barrier before used index update

2015-10-20 Thread Nikita Kalyazin
Descriptors that have been put into the used vring must be observable by guest earlier than the new used index value. Although compiler barrier serves well for Intel architectue here, the proper cross-platform solution is to use write barrier before the used index is updated. Signed-off-by: Nikita

[dpdk-dev] [PATCH] vhost: call write barrier before used index update

2015-10-20 Thread Bruce Richardson
On Tue, Oct 20, 2015 at 05:07:46PM +0300, Nikita Kalyazin wrote: > Descriptors that have been put into the used vring must be observable by > guest earlier than the new used index value. > Although compiler barrier serves well for Intel architectue here, the > proper cross-platform solution is to u