[dpdk-dev] [PATCH 3/5] virtio: use indirect ring elements

2015-10-30 Thread Thomas Monjalon
Sorry there is a gcc error. 2015-10-18 22:16, Stephen Hemminger: > + for (i = 0; i < vq_size; i++) { virtio_ethdev.c:386:17: error: comparison between signed and unsigned integer expressions

[dpdk-dev] [PATCH 3/5] virtio: use indirect ring elements

2015-10-19 Thread Xie, Huawei
On 10/19/2015 11:47 PM, Stephen Hemminger wrote: > On Mon, 19 Oct 2015 13:19:50 + > "Xie, Huawei" wrote: > >>> static int >>> -virtqueue_enqueue_xmit(struct virtqueue *txvq, struct rte_mbuf *cookie) >>> +virtqueue_enqueue_xmit(struct virtqueue *txvq, struct rte_mbuf *cookie, >>> +

[dpdk-dev] [PATCH 3/5] virtio: use indirect ring elements

2015-10-19 Thread Xie, Huawei
On 10/19/2015 1:16 PM, Stephen Hemminger wrote: > The virtio ring in QEMU/KVM is usually limited to 256 entries > and the normal way that virtio driver was queuing mbufs required > nsegs + 1 ring elements. By using the indirect ring element feature > if available, each packet will take only one rin

[dpdk-dev] [PATCH 3/5] virtio: use indirect ring elements

2015-10-19 Thread Stephen Hemminger
On Mon, 19 Oct 2015 13:19:50 + "Xie, Huawei" wrote: > > static int > > -virtqueue_enqueue_xmit(struct virtqueue *txvq, struct rte_mbuf *cookie) > > +virtqueue_enqueue_xmit(struct virtqueue *txvq, struct rte_mbuf *cookie, > > + int use_indirect) > > { > > struct vq_desc_

[dpdk-dev] [PATCH 3/5] virtio: use indirect ring elements

2015-10-18 Thread Stephen Hemminger
The virtio ring in QEMU/KVM is usually limited to 256 entries and the normal way that virtio driver was queuing mbufs required nsegs + 1 ring elements. By using the indirect ring element feature if available, each packet will take only one ring slot even for multi-segment packets. Signed-off-by: S