DPDK patches and discussions
 help / color / mirror / Atom feed
From: Wei Wang <wei.w.wang@intel.com>
To: Yuanhan Liu <yliu@fridaylinux.org>,
	 "Yang, Zhiyong" <zhiyong.yang@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	 "maxime.coquelin@redhat.com" <maxime.coquelin@redhat.com>,
	"Tan, Jianfeng" <jianfeng.tan@intel.com>
Subject: Re: [dpdk-dev] [PATCH 00/11] net/vhostpci: A new vhostpci PMD supporting VM2VM scenario
Date: Wed, 06 Dec 2017 11:00:21 +0800	[thread overview]
Message-ID: <5A275D45.8050505@intel.com> (raw)
In-Reply-To: <20171205140838.GE9111@yliu-dev>

On 12/05/2017 10:08 PM, Yuanhan Liu wrote:
> On Tue, Dec 05, 2017 at 06:59:26AM +0000, Yang, Zhiyong wrote:
>> Hi all,
>>
>>> -----Original Message-----
>>> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Zhiyong Yang
>>> Sent: Thursday, November 30, 2017 5:47 PM
>>> To: dev@dpdk.org; yliu@fridaylinux.org; maxime.coquelin@redhat.com
>>> Cc: Wang, Wei W <wei.w.wang@intel.com>; Tan, Jianfeng
>>> <jianfeng.tan@intel.com>
>>> Subject: [dpdk-dev] [PATCH 00/11] net/vhostpci: A new vhostpci PMD
>>> supporting VM2VM scenario
>>>
>>> Vhostpci PMD is a new type driver working in guest OS which has ability to drive
>>> the vhostpci modern pci device, which is a new virtio device.
>>>
>>> The following linking is about vhostpci design:
>>>
>>> An initial device design is presented at KVM Forum'16:
>>> http://www.linux-kvm.org/images/5/55/02x07A-Wei_Wang-Design_of-Vhost-
>>> pci.pdf
>>> The latest device design and implementation will be posted to the QEMU
>>> community soon.
>>>
>> The latest version vhostpci device code has been posted to QEMU community.
>> [PATCH v3 0/7] Vhost-pci for inter-VM communication
>> http://lists.nongnu.org/archive/html/qemu-devel/2017-12/msg00494.html
> I didn't follow on the qemu ML. Do you know when it's likely it will
> get accepted?
>
> 	--yliu

Hi Yuanhan,

There appear to be more people interested in this solution. My 
expectation is to get the fundamental part of device finalized in 3 months.

For the pmd patches, I think it would be great if people can start the 
review from the non-device related part (e.g. the data transmission logic).

Best,
Wei

  reply	other threads:[~2017-12-06  2:58 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-30  9:46 Zhiyong Yang
2017-11-30  9:46 ` [dpdk-dev] [PATCH 01/11] drivers/net: add vhostpci PMD base files Zhiyong Yang
2017-11-30  9:46 ` [dpdk-dev] [PATCH 02/11] net/vhostpci: public header files Zhiyong Yang
2017-11-30  9:46 ` [dpdk-dev] [PATCH 03/11] net/vhostpci: add debugging log macros Zhiyong Yang
2017-11-30  9:46 ` [dpdk-dev] [PATCH 04/11] net/vhostpci: add basic framework Zhiyong Yang
2017-11-30  9:46 ` [dpdk-dev] [PATCH 05/11] net/vhostpci: add queue setup Zhiyong Yang
2017-11-30  9:46 ` [dpdk-dev] [PATCH 06/11] net/vhostpci: add support for link status change Zhiyong Yang
2017-11-30  9:46 ` [dpdk-dev] [PATCH 07/11] net/vhostpci: get remote memory region and vring info Zhiyong Yang
2017-11-30  9:46 ` [dpdk-dev] [PATCH 08/11] net/vhostpci: add RX function Zhiyong Yang
2017-11-30  9:46 ` [dpdk-dev] [PATCH 09/11] net/vhostpci: add TX function Zhiyong Yang
2017-11-30  9:46 ` [dpdk-dev] [PATCH 10/11] net/vhostpci: support RX/TX packets statistics Zhiyong Yang
2017-11-30  9:46 ` [dpdk-dev] [PATCH 11/11] net/vhostpci: update release note Zhiyong Yang
2017-12-05  6:59 ` [dpdk-dev] [PATCH 00/11] net/vhostpci: A new vhostpci PMD supporting VM2VM scenario Yang, Zhiyong
2017-12-05 14:08   ` Yuanhan Liu
2017-12-06  3:00     ` Wei Wang [this message]
2017-12-07  6:07   ` Yang, Zhiyong
2017-12-19 11:14 ` Maxime Coquelin
2017-12-20  1:51   ` Yang, Zhiyong
2017-12-21  5:52     ` Tan, Jianfeng
2017-12-21  6:21       ` Yang, Zhiyong
2017-12-21  6:26         ` Yang, Zhiyong
2017-12-21  8:26           ` Maxime Coquelin
2017-12-21  8:40             ` Yang, Zhiyong
2018-01-11 11:13   ` Yang, Zhiyong
2018-01-18  9:04     ` Maxime Coquelin
2018-01-19  1:56       ` Yang, Zhiyong

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=5A275D45.8050505@intel.com \
    --to=wei.w.wang@intel.com \
    --cc=dev@dpdk.org \
    --cc=jianfeng.tan@intel.com \
    --cc=maxime.coquelin@redhat.com \
    --cc=yliu@fridaylinux.org \
    --cc=zhiyong.yang@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).