From: "Ouyang, Changchun" <changchun.ouyang@intel.com>
To: "Xie, Huawei" <huawei.xie@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC] lib/librte_vhost: qemu vhost-user support into DPDK vhost library
Date: Wed, 27 Aug 2014 00:43:49 +0000 [thread overview]
Message-ID: <F52918179C57134FAEC9EA62FA2F96251183B590@shsmsx102.ccr.corp.intel.com> (raw)
In-Reply-To: <C37D651A908B024F974696C65296B57B0F27BC38@SHSMSX101.ccr.corp.intel.com>
Do we have performance comparison between both implementation?
Thanks
Changchun
-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Xie, Huawei
Sent: Tuesday, August 26, 2014 7:06 PM
To: dev@dpdk.org
Subject: Re: [dpdk-dev] [RFC] lib/librte_vhost: qemu vhost-user support into DPDK vhost library
Hi all:
We are implementing qemu official vhost-user interface into DPDK vhost library, so there would be two coexisting implementations for user space vhost backend.
Pro and cons in my mind:
Existing solution:
Pros: works with qemu version before 2.1; Cons: depends on eventfd proxy kernel module and extra maintenance effort Qemu vhost-user:
Pros: qemu official us-vhost interface; Cons: only available after qemu 2.1
BR.
huawei
next prev parent reply other threads:[~2014-08-27 0:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-26 11:05 Xie, Huawei
2014-08-27 0:43 ` Ouyang, Changchun [this message]
2014-08-27 4:39 ` Tetsuya.Mukawa
2014-08-27 5:01 ` Ouyang, Changchun
2014-08-27 5:27 ` Tetsuya.Mukawa
2014-08-27 5:56 ` Xie, Huawei
2014-08-27 6:07 ` Tetsuya.Mukawa
2014-08-27 5:58 ` Tetsuya.Mukawa
2014-08-27 6:00 ` Ouyang, Changchun
2014-08-27 6:09 ` Tetsuya.Mukawa
2014-09-13 5:27 ` Linhaifeng
2014-09-16 1:36 ` 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=F52918179C57134FAEC9EA62FA2F96251183B590@shsmsx102.ccr.corp.intel.com \
--to=changchun.ouyang@intel.com \
--cc=dev@dpdk.org \
--cc=huawei.xie@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).