From: "Xie, Huawei" <huawei.xie@intel.com>
To: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH v4 0/5] lib/librte_vhost: user space vhost cuse driver library
Date: Fri, 12 Sep 2014 11:07:26 +0000 [thread overview]
Message-ID: <C37D651A908B024F974696C65296B57B0F29BF3F@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <1410519304-14521-1-git-send-email-huawei.xie@intel.com>
Hi all:
We had generated fixes for plenty of coding style issues in the old vhost example code,
and will re-generate the fixes for coding style issue once this patch is applied. This patch focuses
and only focuses on refactoring vhost example to a library. Any existing issue will be fixed in separate
patches, for example, like structure assignment rather than memcpy Stephen ever mentioned.
Appreciate your comments.
Best Regards
-huawei
> -----Original Message-----
> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Huawei Xie
> Sent: Friday, September 12, 2014 6:55 PM
> To: dev@dpdk.org
> Subject: [dpdk-dev] [PATCH v4 0/5] lib/librte_vhost: user space vhost cuse
> driver library
>
> This set of patches transforms and refactors vhost example to a user
> space vhost cuse library. This library implements a user space vhost
> cuse driver, and provides generic APIs for user space ethernet vswitch
> to integrate us-vhost for fast packet switching with guest virtio.
>
> Change notes:
>
> v2) Turn off vhost lib by default
>
> v3) Fixed checkpatch issues
>
> v4) Split the patch per Thomas's requirement
>
>
> Huawei Xie (5):
> mv vhost example to vhost lib directory
> copy the vhost rx/tx functions from main.c to new file vhost_rxtx.c
> remove main.c main.h
> remove Makefile
> rename virtio-net.h to rte_virtio_net.h as API header file
> vmdq, mac learning and other switch related logics are removed
> zero copy feature isn't generic,and is removed.
> add vhost lib Makefile.
> Add TODOs for found new issues.
> Fix coding style issue which are treated as errors by checkpatch.pl
> add vhost lib support in makefile
> turn off vhost lib by default as it requires fuse development package.
>
> config/common_linuxapp | 7 +
> examples/vhost/Makefile | 60 -
> examples/vhost/eventfd_link/Makefile | 39 -
> examples/vhost/eventfd_link/eventfd_link.c | 205 --
> examples/vhost/eventfd_link/eventfd_link.h | 79 -
> examples/vhost/libvirt/qemu-wrap.py | 367 ---
> examples/vhost/main.c | 3722 --------------------------
> examples/vhost/main.h | 86 -
> examples/vhost/vhost-net-cdev.c | 367 ---
> examples/vhost/vhost-net-cdev.h | 83 -
> examples/vhost/virtio-net.c | 1165 --------
> examples/vhost/virtio-net.h | 161 --
> lib/Makefile | 1 +
> lib/librte_vhost/Makefile | 48 +
> lib/librte_vhost/eventfd_link/Makefile | 39 +
> lib/librte_vhost/eventfd_link/eventfd_link.c | 205 ++
> lib/librte_vhost/eventfd_link/eventfd_link.h | 79 +
> lib/librte_vhost/libvirt/qemu-wrap.py | 367 +++
> lib/librte_vhost/rte_virtio_net.h | 192 ++
> lib/librte_vhost/vhost-net-cdev.c | 362 +++
> lib/librte_vhost/vhost-net-cdev.h | 112 +
> lib/librte_vhost/vhost_rxtx.c | 301 +++
> lib/librte_vhost/virtio-net.c | 1000 +++++++
> mk/rte.app.mk | 5 +
> 24 files changed, 2718 insertions(+), 6334 deletions(-)
> delete mode 100644 examples/vhost/Makefile
> delete mode 100644 examples/vhost/eventfd_link/Makefile
> delete mode 100644 examples/vhost/eventfd_link/eventfd_link.c
> delete mode 100644 examples/vhost/eventfd_link/eventfd_link.h
> delete mode 100755 examples/vhost/libvirt/qemu-wrap.py
> delete mode 100644 examples/vhost/main.c
> delete mode 100644 examples/vhost/main.h
> delete mode 100644 examples/vhost/vhost-net-cdev.c
> delete mode 100644 examples/vhost/vhost-net-cdev.h
> delete mode 100644 examples/vhost/virtio-net.c
> delete mode 100644 examples/vhost/virtio-net.h
> create mode 100644 lib/librte_vhost/Makefile
> create mode 100644 lib/librte_vhost/eventfd_link/Makefile
> create mode 100644 lib/librte_vhost/eventfd_link/eventfd_link.c
> create mode 100644 lib/librte_vhost/eventfd_link/eventfd_link.h
> create mode 100755 lib/librte_vhost/libvirt/qemu-wrap.py
> create mode 100644 lib/librte_vhost/rte_virtio_net.h
> create mode 100644 lib/librte_vhost/vhost-net-cdev.c
> create mode 100644 lib/librte_vhost/vhost-net-cdev.h
> create mode 100644 lib/librte_vhost/vhost_rxtx.c
> create mode 100644 lib/librte_vhost/virtio-net.c
>
> --
> 1.8.1.4
next prev parent reply other threads:[~2014-09-12 11:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-12 10:54 Huawei Xie
2014-09-12 10:55 ` [dpdk-dev] [PATCH v4 1/5] lib/librte_vhost: mv vhost example to vhost lib directory for further code re-factoring Huawei Xie
2014-09-12 10:55 ` [dpdk-dev] [PATCH v4 2/5] lib/librte_vhost: re-factor vhost lib for subsequent transform Huawei Xie
2014-09-12 10:55 ` [dpdk-dev] [PATCH v4 3/5] lib/librte_vhost: vhost lib refactor Huawei Xie
2014-09-12 10:55 ` [dpdk-dev] [PATCH v4 4/5] coding style issue fix Huawei Xie
2014-09-12 10:55 ` [dpdk-dev] [PATCH v4 5/5] lib/librte_vhost: add vhost lib support in makefile Huawei Xie
2014-09-13 4:57 ` Linhaifeng
2014-09-12 11:07 ` Xie, Huawei [this message]
2014-09-23 16:07 ` [dpdk-dev] [PATCH v4 0/5] lib/librte_vhost: user space vhost cuse driver library Xie, Huawei
2014-09-24 14:32 ` Ouyang, Changchun
2014-09-24 16:21 ` Thomas Monjalon
2014-09-25 3:09 ` Xie, Huawei
2014-09-25 14:27 ` Xie, Huawei
2014-09-25 18:00 ` Xie, Huawei
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=C37D651A908B024F974696C65296B57B0F29BF3F@SHSMSX101.ccr.corp.intel.com \
--to=huawei.xie@intel.com \
--cc=dev@dpdk.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).