From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by dpdk.org (Postfix) with ESMTP id 7AB291150 for ; Thu, 17 Jan 2019 16:13:34 +0100 (CET) X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from orsmga001.jf.intel.com ([10.7.209.18]) by orsmga105.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 17 Jan 2019 07:13:33 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,489,1539673200"; d="scan'208";a="128581985" Received: from yexl-server.sh.intel.com (HELO localhost) ([10.67.110.206]) by orsmga001.jf.intel.com with ESMTP; 17 Jan 2019 07:13:31 -0800 Date: Thu, 17 Jan 2019 23:13:27 +0800 From: Ye Xiaolong To: Shahaf Shuler Cc: "dev@dpdk.org" , Maxime Coquelin , Tiwei Bie , Zhihong Wang , "xiao.w.wang@intel.com" , Rami Rosen , Wang Haiyue Message-ID: <20190117151327.GA54315@intel.com> References: <20180928112344.42791-1-xiaolong.ye@intel.com> <20180928214747.48938-1-xiaolong.ye@intel.com> <20180928214747.48938-3-xiaolong.ye@intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.9.4 (2018-02-28) Subject: Re: [dpdk-dev] [PATCH v8 2/2] examples/vdpa: introduce a new sample for vDPA X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jan 2019 15:13:34 -0000 Hi, On 01/17, Shahaf Shuler wrote: >Hi, > >Going back to this merged commit, > >Saturday, September 29, 2018 12:48 AM, Xiaolong Ye: >> Subject: [dpdk-dev] [PATCH v8 2/2] examples/vdpa: introduce a new sample >> for vDPA >> >> The vdpa sample application creates vhost-user sockets by using the vDPA >> backend. vDPA stands for vhost Data Path Acceleration which utilizes virtio >> ring compatible devices to serve virtio driver directly to enable datapath >> acceleration. As vDPA driver can help to set up vhost datapath, this >> application doesn't need to launch dedicated worker threads for vhost >> enqueue/dequeue operations. >> >> Signed-off-by: Xiaolong Ye >> Acked-by: Xiao Wang >> Reviewed-by: Maxime Coquelin >> --- > >[...] > >> + >> +Start the VMs >> +~~~~~~~~~~~~~ >> + >> +.. code-block:: console >> + >> + qemu-system-x86_64 -cpu host -enable-kvm \ >> + >> + -mem-prealloc \ >> + -chardev socket,id=char0,path= \ >> + -netdev type=vhost-user,id=vdpa,chardev=char0 \ >> + -device >> + virtio-net-pci,netdev=vdpa,mac=00:aa:bb:cc:dd:ee,page-per-vq=on \ > > >It doesn't seems like qemu has the id=vdpa and netdev=vdpa options. >Grepping vdpa on qemu returns empty. > >Am using QEMU v3.1.0-513-gfb177a0. Commit head is fb177a036f2e ("MAINTAINERS: Mark RISC-V as Supported"). > >Did I missed anything? > Not quite sure about your question here, the vdpa used in above qemu cmdline is just a normal string, you can replace it with other string like -netdev type=vhost-user,id=mynet,chardev=char0 \ -device virtio-net-pci,netdev=mynet,... The major support for vdpa is done in dpdk side as the vhost user backend, qemu will use normal vhost user protocol to communicate with it. Thanks, Xiaolong