From: "Liu, Yong" <yong.liu@intel.com>
To: "Xu, Qian Q" <qian.q.xu@intel.com>, "dts@dpdk.org" <dts@dpdk.org>
Subject: Re: [dts] [PATCH v2 0/5]Add vhost-user and vhost-cuse one vm sample case
Date: Mon, 13 Jul 2015 07:58:24 +0000 [thread overview]
Message-ID: <86228AFD5BCD8E4EBFD2B90117B5E81E10E6039E@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <1436770794-6559-1-git-send-email-qian.q.xu@intel.com>
Thanks Qian. Applied in 1.1 branch.
> -----Original Message-----
> From: dts [mailto:dts-bounces@dpdk.org] On Behalf Of Qian Xu
> Sent: Monday, July 13, 2015 3:00 PM
> To: dts@dpdk.org
> Subject: [dts] [PATCH v2 0/5]Add vhost-user and vhost-cuse one vm sample
> case
>
> This patchset will enable vhost-user and vhost-cuse sample one-vm
> performance ca ses based on the virtualization framework. The vhost-
> user's implementation is ba sed on vhost user socket, while the vhost-
> cuse is via IOCTL messages.
> The patchset includes below things:
> 1. Vhost-user sample automation has 4 cases: one VM with dpdk fwd, one VM
> with d pdk fwd with jumboframe enabled, one VM with legacy fwd, one VM
> with legacy fwd with jumboframe enabled.
> 2. Vhost-cuse sample automation has similar 4 cases as above.
> 3. The required qemu version fo vhost-user is >=qemu2.2
> 4. The one-vm has 2 virtio, and the vhost has binded to one physical port.
> 5. update qemu_kvm.py to support vhost-cuse.
> 6. vhost_cuse_sample.cfg and vhost_sample.cfg are the config file for
> references .
>
> v2 changes:
> 1. Remove unnecessary codes and debug codes.
> 2. use pep8 to align the codes format.
> 3. minor update about the core numbers of vhost usage. Set 1S/3C/1T as
> default core setting for vhost to get best perf.
> 4. change the vm core numbers to 2cores in the config files.
>
>
> Qian Xu (5):
> add vhost-cuse implementations for virtio pci device
> add vhost-cuse sample config file for reference
> add vhost-user sample config file for reference
> add vhost-cuse one vm sample
> add vhost-user one vm sample test
>
> conf/vhost_cuse_sample.cfg | 14 ++
> conf/vhost_sample.cfg | 14 ++
> framework/qemu_kvm.py | 22 +-
> tests/TestSuite_vhost_cuse_sample.py | 455
> +++++++++++++++++++++++++++++++++++
> tests/TestSuite_vhost_sample.py | 428
> ++++++++++++++++++++++++++++++++
> 5 files changed, 932 insertions(+), 1 deletion(-)
> create mode 100644 conf/vhost_cuse_sample.cfg
> create mode 100644 conf/vhost_sample.cfg
> create mode 100644 tests/TestSuite_vhost_cuse_sample.py
> create mode 100644 tests/TestSuite_vhost_sample.py
>
> --
> 2.1.0
prev parent reply other threads:[~2015-07-13 7:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-13 6:59 Qian Xu
2015-07-13 6:59 ` [dts] [PATCH v2 1/5] add vhost-cuse implementations for virtio pci device Qian Xu
2015-07-13 6:59 ` [dts] [PATCH v2 2/5] add vhost-cuse sample config file for reference Qian Xu
2015-07-13 6:59 ` [dts] [PATCH v2 3/5] add vhost-user " Qian Xu
2015-07-13 6:59 ` [dts] [PATCH v2 4/5] add vhost-cuse one vm sample Qian Xu
2015-07-13 6:59 ` [dts] [PATCH v2 5/5] add vhost-user one vm sample test Qian Xu
2015-07-13 7:58 ` Liu, Yong [this message]
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=86228AFD5BCD8E4EBFD2B90117B5E81E10E6039E@SHSMSX103.ccr.corp.intel.com \
--to=yong.liu@intel.com \
--cc=dts@dpdk.org \
--cc=qian.q.xu@intel.com \
/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).