ion at lists.linux-foundation.org
> Subject: Re: [dpdk-dev] [snabb-devel] Re: memory barriers in virtq.lua?
>
> Howdy,
>
> On 8 April 2015 at 17:15, Xie, Huawei wrote:
>
> > luke:
> > 1. host read the flag. 2 guest toggles the flag 3.guest checks the used.
> > 4.
Howdy,
On 8 April 2015 at 17:15, Xie, Huawei wrote:
> luke:
> 1. host read the flag. 2 guest toggles the flag 3.guest checks the used.
> 4. host update used.
> Is this your case?
>
Yep, that is exactly the case I mean.
Cheers,
-Luke
On 4/7/2015 10:23 PM, Luke Gorrie wrote:
> 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
On 7 April 2015 at 17:30, Michael S. Tsirkin wrote:
> Just guessing from the available info:
>
> I think you refer to this:
> The driver MUST handle spurious interrupts from the device.
>
> The intent is to be able to handle some spurious interrupts once in a
> while. AFAIK linux
On Tue, Apr 07, 2015 at 04:22:42PM +0200, Luke Gorrie wrote:
> 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
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
6 matches
Mail list logo