Message ID | 20190829141224.49700-1-jin.yu@intel.com (mailing list archive) |
---|---|
Headers |
Return-Path: <dev-bounces@dpdk.org> X-Original-To: patchwork@dpdk.org Delivered-To: patchwork@dpdk.org Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 26E2B1C298; Thu, 29 Aug 2019 08:26:55 +0200 (CEST) Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 182B41C295 for <dev@dpdk.org>; Thu, 29 Aug 2019 08:26:53 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from fmsmga007.fm.intel.com ([10.253.24.52]) by fmsmga103.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Aug 2019 23:26:53 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.64,442,1559545200"; d="scan'208";a="182252042" Received: from storage36.sh.intel.com ([10.67.110.166]) by fmsmga007.fm.intel.com with ESMTP; 28 Aug 2019 23:26:51 -0700 From: JinYu <jin.yu@intel.com> To: dev@dpdk.org Cc: changpeng.liu@intel.com, maxime.coquelin@redhat.com, tiwei.bie@intel.com, zhihong.wang@intel.com, JinYu <jin.yu@intel.com> Date: Thu, 29 Aug 2019 22:12:14 +0800 Message-Id: <20190829141224.49700-1-jin.yu@intel.com> X-Mailer: git-send-email 2.17.2 In-Reply-To: <20190806182500.22320> References: <20190806182500.22320> Subject: [dpdk-dev] [PATCH v6 00/10] vhost: support inflight share memory protocol feature X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Sender: "dev" <dev-bounces@dpdk.org> |
Series |
vhost: support inflight share memory protocol feature
|
|
Message
Jin Yu
Aug. 29, 2019, 2:12 p.m. UTC
This patches introduces two new messages VHOST_USER_GET_INFLIGHT_FD and VHOST_USER_SET_INFLIGHT_FD to support transferring a shared buffer between qemu and backend for backend reconnection. Now It can both support split and packed ring. The example code show how these APIs work. The test has passed. How to test the example: 1, Qemu need a patch. https://patchwork.kernel.org/patch/10861411/ it also needs some manual modifications: we should confirm that before we send get inflight we have already sent the set features but it seems Qemu didn't do like this. So we manually revise this, we can add below code in vhost_dev_get_inflight int r; r = vhost_dev_set_features(dev, dev->log_enabled); if (r < 0) { return -errno; } before get_inflight_fd. 2, Guest OS version >= 5.0 3, run the example 4, run the qemu with vhost-user-blk-pci. eg: -chardev socket,id=spdk_vhost_blk0,reconnect=1,path=xxxx\ -device vhost-user-blk-pci,ring_packed=on,chardev=spdk_vhost_blk0,num-queues=1\ 5, run fio in the guest 6, kill the example and run again. 7, the fio in the guest should continue run without errors. JinYu (10): vhost: add the inflight description vhost: add packed ring vhost: add the inflight structure vhost: add two new messages to support a shared buffer vhost: checkout and cleanup the resubmit inflight information vhost: add the APIs to operate inflight ring vhost: add APIs for user getting inflight ring vhost: fix vring functions to support packed ring vhost: add an API for judging vq format vhost: add vhost-user-blk example which support inflight examples/vhost_blk/Makefile | 67 ++ examples/vhost_blk/blk.c | 125 +++ examples/vhost_blk/blk_spec.h | 95 ++ examples/vhost_blk/meson.build | 20 + examples/vhost_blk/vhost_blk.c | 1313 +++++++++++++++++++++++++ examples/vhost_blk/vhost_blk.h | 116 +++ examples/vhost_blk/vhost_blk_compat.c | 195 ++++ lib/librte_vhost/rte_vhost.h | 250 ++++- lib/librte_vhost/vhost.c | 396 +++++++- lib/librte_vhost/vhost.h | 16 + lib/librte_vhost/vhost_user.c | 439 +++++++++ lib/librte_vhost/vhost_user.h | 12 +- 12 files changed, 3032 insertions(+), 12 deletions(-) create mode 100644 examples/vhost_blk/Makefile create mode 100644 examples/vhost_blk/blk.c create mode 100644 examples/vhost_blk/blk_spec.h create mode 100644 examples/vhost_blk/meson.build create mode 100644 examples/vhost_blk/vhost_blk.c create mode 100644 examples/vhost_blk/vhost_blk.h create mode 100644 examples/vhost_blk/vhost_blk_compat.c
Comments
Hi Jin, I see in this patch set there are several callings rte_compiler_barrier() which is sufficient for x86 but not for aarch64/ppc and other weaker memory model architectures. EAL has defined coherent memory io barriers(I think this should be the right barrier) for mutli-arch support. Could you change these barriers to rte_cio_r/wmb barriers? http://git.dpdk.org/dpdk/tree/lib/librte_eal/common/include/generic/rte_atomic.h#n110 Best Regards, Gavin > -----Original Message----- > From: dev <dev-bounces@dpdk.org> On Behalf Of JinYu > Sent: Thursday, August 29, 2019 10:12 PM > To: dev@dpdk.org > Cc: changpeng.liu@intel.com; maxime.coquelin@redhat.com; > tiwei.bie@intel.com; zhihong.wang@intel.com; JinYu <jin.yu@intel.com> > Subject: [dpdk-dev] [PATCH v6 00/10] vhost: support inflight share memory > protocol feature > > This patches introduces two new messages > VHOST_USER_GET_INFLIGHT_FD > and VHOST_USER_SET_INFLIGHT_FD to support transferring a shared > buffer between qemu and backend for backend reconnection. > Now It can both support split and packed ring. The example code show > how these APIs work. The test has passed. > > How to test the example: > 1, Qemu need a patch. > https://patchwork.kernel.org/patch/10861411/ > it also needs some manual modifications: > we should confirm that before we send get inflight we have already > sent the set features but it seems Qemu didn't do like this. So we > manually revise this, we can add below code in vhost_dev_get_inflight > int r; > > r = vhost_dev_set_features(dev, dev->log_enabled); > if (r < 0) { > return -errno; > } > before get_inflight_fd. > 2, Guest OS version >= 5.0 > 3, run the example > 4, run the qemu with vhost-user-blk-pci. > eg: > -chardev socket,id=spdk_vhost_blk0,reconnect=1,path=xxxx\ > -device vhost-user-blk- > pci,ring_packed=on,chardev=spdk_vhost_blk0,num-queues=1\ > 5, run fio in the guest > 6, kill the example and run again. > 7, the fio in the guest should continue run without errors. > > JinYu (10): > vhost: add the inflight description > vhost: add packed ring > vhost: add the inflight structure > vhost: add two new messages to support a shared buffer > vhost: checkout and cleanup the resubmit inflight information > vhost: add the APIs to operate inflight ring > vhost: add APIs for user getting inflight ring > vhost: fix vring functions to support packed ring > vhost: add an API for judging vq format > vhost: add vhost-user-blk example which support inflight > > examples/vhost_blk/Makefile | 67 ++ > examples/vhost_blk/blk.c | 125 +++ > examples/vhost_blk/blk_spec.h | 95 ++ > examples/vhost_blk/meson.build | 20 + > examples/vhost_blk/vhost_blk.c | 1313 +++++++++++++++++++++++++ > examples/vhost_blk/vhost_blk.h | 116 +++ > examples/vhost_blk/vhost_blk_compat.c | 195 ++++ > lib/librte_vhost/rte_vhost.h | 250 ++++- > lib/librte_vhost/vhost.c | 396 +++++++- > lib/librte_vhost/vhost.h | 16 + > lib/librte_vhost/vhost_user.c | 439 +++++++++ > lib/librte_vhost/vhost_user.h | 12 +- > 12 files changed, 3032 insertions(+), 12 deletions(-) > create mode 100644 examples/vhost_blk/Makefile > create mode 100644 examples/vhost_blk/blk.c > create mode 100644 examples/vhost_blk/blk_spec.h > create mode 100644 examples/vhost_blk/meson.build > create mode 100644 examples/vhost_blk/vhost_blk.c > create mode 100644 examples/vhost_blk/vhost_blk.h > create mode 100644 examples/vhost_blk/vhost_blk_compat.c > > -- > 2.17.2 IMPORTANT NOTICE: The contents of this email and any attachments are confidential and may also be privileged. If you are not the intended recipient, please notify the sender immediately and do not disclose the contents to any other person, use it for any purpose, or store or copy the information in any medium. Thank you.
On 8/29/19 4:12 PM, JinYu wrote: > This patches introduces two new messages VHOST_USER_GET_INFLIGHT_FD > and VHOST_USER_SET_INFLIGHT_FD to support transferring a shared > buffer between qemu and backend for backend reconnection. > Now It can both support split and packed ring. The example code show > how these APIs work. The test has passed. > > How to test the example: > 1, Qemu need a patch. > https://patchwork.kernel.org/patch/10861411/ > it also needs some manual modifications: > we should confirm that before we send get inflight we have already > sent the set features but it seems Qemu didn't do like this. So we > manually revise this, we can add below code in vhost_dev_get_inflight > int r; > > r = vhost_dev_set_features(dev, dev->log_enabled); > if (r < 0) { > return -errno; > } Are you working on fixing that upstream? What happens if we don't do these modifications and apply your series? Would it be considered as a regression?
> -----Original Message----- > From: Maxime Coquelin [mailto:maxime.coquelin@redhat.com] > Sent: Saturday, September 7, 2019 12:36 AM > To: Yu, Jin <jin.yu@intel.com>; dev@dpdk.org > Cc: Liu, Changpeng <changpeng.liu@intel.com>; Bie, Tiwei > <tiwei.bie@intel.com>; Wang, Zhihong <zhihong.wang@intel.com> > Subject: Re: [PATCH v6 00/10] vhost: support inflight share memory protocol > feature > > > > On 8/29/19 4:12 PM, JinYu wrote: > > This patches introduces two new messages > VHOST_USER_GET_INFLIGHT_FD > > and VHOST_USER_SET_INFLIGHT_FD to support transferring a shared > buffer > > between qemu and backend for backend reconnection. > > Now It can both support split and packed ring. The example code show > > how these APIs work. The test has passed. > > > > How to test the example: > > 1, Qemu need a patch. > > https://patchwork.kernel.org/patch/10861411/ > > it also needs some manual modifications: > > we should confirm that before we send get inflight we have already > > sent the set features but it seems Qemu didn't do like this. So we > > manually revise this, we can add below code in vhost_dev_get_inflight > > int r; > > > > r = vhost_dev_set_features(dev, dev->log_enabled); > > if (r < 0) { > > return -errno; > > } > > Are you working on fixing that upstream? > What happens if we don't do these modifications and apply your series? > Would it be considered as a regression? Hi Maxime, Actually I didn't fix the upstream. Without these modifications, get_inflight_fd and set_inflight_fd can't confirm the dev packet format. So the inflight ring format may always be split. Thanks.