I'm a little concerned if it's a correct way to change the name from release to release, some users may use eth_vhost for the driver, and found it was not working. Do we need also make the consistency b/w releases? What's the name difference b/w eth and net? Other PMDs are not virtual devices. Virtio_user is also a virtual device, do we need to change the name,too?
-----Original Message----- From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Xu, Qian Q Sent: Monday, October 10, 2016 11:23 AM To: Maxime Coquelin <maxime.coquelin at redhat.com>; Yuanhan Liu <yuanhan.liu at linux.intel.com> Cc: dev at dpdk.org Subject: Re: [dpdk-dev] [PATCH v2 4/7] vhost: add dequeue zero copy Oh, thx for the info, it's better to have some documentation update in R16.11 release notes. -----Original Message----- From: Maxime Coquelin [mailto:maxime.coque...@redhat.com] Sent: Monday, October 10, 2016 11:14 AM To: Xu, Qian Q <qian.q.xu at intel.com>; Yuanhan Liu <yuanhan.liu at linux.intel.com> Cc: dev at dpdk.org Subject: Re: [dpdk-dev] [PATCH v2 4/7] vhost: add dequeue zero copy Hi Xu, On 10/10/2016 12:12 PM, Xu, Qian Q wrote: > Good to know. I will try v3. BTW, on the master branch, seems vhost PMD is > broken. When we run --vdev 'eth_vhost0,xxxx', then it will report the error > that the driver is not supported. V16.07 is OK, but I haven't got time to do > git bisect. Name has been chenged to net_vhost0 for consistency with other PMDs. Maxime
