search for: 6e390f6e

...ag 3.guest checks the used. > 4. host update used. > Is this your case? > Yep, that is exactly the case I mean. Cheers, -Luke -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfoundation.org/pipermail/virtualization/attachments/20150409/6e390f6e/attachment.html>

...ag 3.guest checks the used. > 4. host update used. > Is this your case? > Yep, that is exactly the case I mean. Cheers, -Luke -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.linuxfoundation.org/pipermail/virtualization/attachments/20150409/6e390f6e/attachment.html>

Hi Michael, I'm writing to follow up the previous discussion about memory barriers in virtio-net device implementations, and Cc'ing the DPDK list because I believe this is relevant to them too. First, thanks again for getting in touch and reviewing our code. I have now found a missed case where we *do* require a hardware memory barrier on x86 in our vhost/virtio-net device. That is when

Hi Michael, I'm writing to follow up the previous discussion about memory barriers in virtio-net device implementations, and Cc'ing the DPDK list because I believe this is relevant to them too. First, thanks again for getting in touch and reviewing our code. I have now found a missed case where we *do* require a hardware memory barrier on x86 in our vhost/virtio-net device. That is when