DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Xie, Huawei" <huawei.xie@intel.com>
To: Linhaifeng <haifeng.lin@huawei.com>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] [RFC] lib/librte_vhost: qemu vhost-user support into DPDK vhost library
Date: Tue, 16 Sep 2014 01:36:29 +0000
Message-ID: <C37D651A908B024F974696C65296B57B0F29E6FE@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <5413D5DA.9030607@huawei.com>

Hi Haifeng:
Might be in the release after 1.8.

> -----Original Message-----
> From: Linhaifeng [mailto:haifeng.lin@huawei.com]
> Sent: Saturday, September 13, 2014 1:28 PM
> To: Xie, Huawei; dev@dpdk.org
> Subject: Re: [dpdk-dev] [RFC] lib/librte_vhost: qemu vhost-user support
> into DPDK vhost library
> 
> when will publish ?
> 
> On 2014/8/26 19:05, Xie, Huawei wrote:
> > 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
> >
> >

      reply	other threads:[~2014-09-16  1:32 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
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 [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=C37D651A908B024F974696C65296B57B0F29E6FE@SHSMSX101.ccr.corp.intel.com \
    --to=huawei.xie@intel.com \
    --cc=dev@dpdk.org \
    --cc=haifeng.lin@huawei.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

DPDK patches and discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/dev/0 dev/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 dev dev/ https://inbox.dpdk.org/dev \
		dev@dpdk.org
	public-inbox-index dev

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.dev


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git