[dpdk-dev] [PATCH v6 04/13] vhost: rxtx: prepare work for multiple queue support

On Tue, Oct 20, 2015 at 08:57:52AM +0200, Thomas Monjalon wrote: > 2015-10-09 13:46, Yuanhan Liu: > > From: Changchun Ouyang > > > > Do not use VIRTIO_RXQ or VIRTIO_TXQ anymore; use the queue_id, > > instead, which will be set to a proper value for a specific queue > > when we have multiple queue

[dpdk-dev] [PATCH v6 04/13] vhost: rxtx: prepare work for multiple queue support

2015-10-20 15:10, Yuanhan Liu: > On Tue, Oct 20, 2015 at 08:57:52AM +0200, Thomas Monjalon wrote: > > > - if (unlikely(queue_id != VIRTIO_RXQ)) { > > > - LOG_DEBUG(VHOST_DATA, "mq isn't supported in this version.\n"); > > > + if (unlikely(!is_valid_virt_queue_idx(queue_id, 0, dev->virt_qp_n

[dpdk-dev] [PATCH v6 04/13] vhost: rxtx: prepare work for multiple queue support

2015-10-09 13:46, Yuanhan Liu: > From: Changchun Ouyang > > Do not use VIRTIO_RXQ or VIRTIO_TXQ anymore; use the queue_id, > instead, which will be set to a proper value for a specific queue > when we have multiple queue support enabled. > > For now, queue_id is still set with VIRTIO_RXQ or VIRT

[dpdk-dev] [PATCH v6 04/13] vhost: rxtx: prepare work for multiple queue support

From: Changchun Ouyang Do not use VIRTIO_RXQ or VIRTIO_TXQ anymore; use the queue_id, instead, which will be set to a proper value for a specific queue when we have multiple queue support enabled. For now, queue_id is still set with VIRTIO_RXQ or VIRTIO_TXQ, so it should not break anything. Sig