[dpdk-dev] [PATCH] virtio: avoid avail ring entry index update if equal

On 4/28/2016 4:14 PM, Thomas Monjalon wrote: > 2016-04-27 23:19, Yuanhan Liu: >> And applied to dpdk-next-virtio, with few tiny changes: >> >> - we normally put suggested/reported-by above the SoB. > Yes we must keep the chronological order in these lines. > Thanks for reminder

[dpdk-dev] [PATCH] virtio: avoid avail ring entry index update if equal

2016-04-27 23:19, Yuanhan Liu: > And applied to dpdk-next-virtio, with few tiny changes: > > - we normally put suggested/reported-by above the SoB. Yes we must keep the chronological order in these lines.

[dpdk-dev] [PATCH] virtio: avoid avail ring entry index update if equal

On Wed, Apr 27, 2016 at 04:53:58AM -0400, Huawei Xie wrote: > Avail ring is updated by the frontend and consumed by the backend. > There are frequent core to core cache transfers for the avail ring. > > This optmization avoids avail ring entry index update if the entry > already holds the same

[dpdk-dev] [PATCH] virtio: avoid avail ring entry index update if equal

Avail ring is updated by the frontend and consumed by the backend. There are frequent core to core cache transfers for the avail ring. This optmization avoids avail ring entry index update if the entry already holds the same value. As DPDK virtio PMD implements FIFO free descriptor list (also for