[dpdk-dev] [PATCH v3] lib/librte_vhost: vhost library support to facilitate integration with DPDK accelerated vswitch.
huawei.xie at intel.com
Fri Aug 29 04:05:51 CEST 2014
> -----Original Message-----
> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com]
> Sent: Friday, August 29, 2014 4:16 AM
> To: Xie, Huawei
> Cc: dev at dpdk.org
> Subject: Re: [dpdk-dev] [PATCH v3] lib/librte_vhost: vhost library support to
> facilitate integration with DPDK accelerated vswitch.
> > config/common_linuxapp | 7 +
> > lib/Makefile | 1 +
> > lib/librte_vhost/Makefile | 48 ++
> > lib/librte_vhost/eventfd_link/Makefile | 39 +
> > lib/librte_vhost/eventfd_link/eventfd_link.c | 194 +++++
> > lib/librte_vhost/eventfd_link/eventfd_link.h | 40 +
> > lib/librte_vhost/rte_virtio_net.h | 192 +++++
> > lib/librte_vhost/vhost-net-cdev.c | 363 ++++++++++
> > lib/librte_vhost/vhost-net-cdev.h | 109 +++
> > lib/librte_vhost/vhost_rxtx.c | 292 ++++++++
> > lib/librte_vhost/virtio-net.c | 1002 ++++++++++++++++++++++++++
> It would help if you made a first patch to move existing code,
> another patch to convert it into a lib, and a last one for
> the new example.
> So it would show how you transform the old example code and
> would be easier to review.
My original order is first patch to add a new lib but not turned on,
another patch to remove the old example, and the third patch to
add the new example.
I am preparing new patch sets, merging the mergable feature, will
follow the suggested order.
More information about the dev