From: Huawei Xie <huawei.xie@intel.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH 0/2] examples/vhost: vhost example based on vhost lib API
Date: Thu, 18 Sep 2014 21:19:48 +0800 [thread overview]
Message-ID: <1411046390-29478-1-git-send-email-huawei.xie@intel.com> (raw)
Old vhost example consists of vhost cuse driver, virtio device management, and
VMDQ based packet switching logic.
vhost cuse driver and virtio device management are moved into vhost lib. This
patch modifies vhost example to use vhost lib API.
Huawei Xie (2):
copy main.c main.h from old vhost example
modify vhost example to use vhost lib API
examples/vhost/Makefile | 52 +
examples/vhost/main.c | 3045 +++++++++++++++++++++++++++++++++++++++++++++++
examples/vhost/main.h | 123 ++
3 files changed, 3220 insertions(+)
create mode 100644 examples/vhost/Makefile
create mode 100644 examples/vhost/main.c
create mode 100644 examples/vhost/main.h
--
1.8.1.4
next reply other threads:[~2014-09-18 13:14 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-18 13:19 Huawei Xie [this message]
2014-09-18 13:19 ` [dpdk-dev] [PATCH 1/2] examples/vhost: copy old vhost example files Huawei Xie
2014-09-18 13:19 ` [dpdk-dev] [PATCH 2/2] examples/vhost: vhost example modification to use vhost lib API Huawei Xie
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=1411046390-29478-1-git-send-email-huawei.xie@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).