search for: usedelem

Displaying 3 results from an estimated 3 matches for "usedelem".

Did you mean: used_elem
[virtio-spec PATCH 0/5] Receiving Used Buffers example code: cleanups and an extra mb()
2013 Jun 08
7
[virtio-spec PATCH 0/5] Receiving Used Buffers example code: cleanups and an extra mb()
...is <http://thread.gmane.org/gmane.comp.bios.tianocore.devel/2804/focus=2819>: [PATCH v3 10/15] OvmfPkg: VirtioNetDxe: implement Tx: SNP.Transmit and SNP.GetStatus On 06/07/13 16:17, Stefan Hajnoczi wrote: > There is no read memory barrier between fetching TxCurUsed and > fetching UsedElem[].Id. In theory I think there is no guarantee that > Dev->TxRing.Used.UsedElem[UsedElemIdx].Id is fetched *after* > Dev->TxRing.Used.Idx. On x86 it shouldn't be a problem but I expected > a read memory barrier after comparing fetching Dev->TxRing.Used.Idx. (Solely for the r...
[virtio-spec PATCH 0/5] Receiving Used Buffers example code: cleanups and an extra mb()
2013 Jun 08
7
[virtio-spec PATCH 0/5] Receiving Used Buffers example code: cleanups and an extra mb()
...is <http://thread.gmane.org/gmane.comp.bios.tianocore.devel/2804/focus=2819>: [PATCH v3 10/15] OvmfPkg: VirtioNetDxe: implement Tx: SNP.Transmit and SNP.GetStatus On 06/07/13 16:17, Stefan Hajnoczi wrote: > There is no read memory barrier between fetching TxCurUsed and > fetching UsedElem[].Id. In theory I think there is no guarantee that > Dev->TxRing.Used.UsedElem[UsedElemIdx].Id is fetched *after* > Dev->TxRing.Used.Idx. On x86 it shouldn't be a problem but I expected > a read memory barrier after comparing fetching Dev->TxRing.Used.Idx. (Solely for the r...
[virtio-spec PATCH 0/5] Receiving Used Buffers example code: cleanups and an extra mb()
2013 Jun 10
0
[virtio-spec PATCH 0/5] Receiving Used Buffers example code: cleanups and an extra mb()
...e.comp.bios.tianocore.devel/2804/focus=2819>: > > [PATCH v3 10/15] > OvmfPkg: VirtioNetDxe: implement Tx: SNP.Transmit and SNP.GetStatus > > On 06/07/13 16:17, Stefan Hajnoczi wrote: > >> There is no read memory barrier between fetching TxCurUsed and >> fetching UsedElem[].Id. In theory I think there is no guarantee that >> Dev->TxRing.Used.UsedElem[UsedElemIdx].Id is fetched *after* >> Dev->TxRing.Used.Idx. On x86 it shouldn't be a problem but I expected >> a read memory barrier after comparing fetching Dev->TxRing.Used.Idx. > &...