From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tyo201.gate.nec.co.jp (TYO201.gate.nec.co.jp [210.143.35.51]) by dpdk.org (Postfix) with ESMTP id 8F138B0B3 for ; Wed, 18 Jun 2014 13:11:20 +0200 (CEST) Received: from mailgate3.nec.co.jp ([10.7.69.197]) by tyo201.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id s5IBBX8k006361; Wed, 18 Jun 2014 20:11:33 +0900 (JST) Received: from mailsv4.nec.co.jp (imss62.nec.co.jp [10.7.69.157]) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) with ESMTP id s5IBBXE20810; Wed, 18 Jun 2014 20:11:33 +0900 (JST) Received: from mail02.kamome.nec.co.jp (mail02.kamome.nec.co.jp [10.25.43.5]) by mailsv4.nec.co.jp (8.13.8/8.13.4) with ESMTP id s5IBBXGu001841; Wed, 18 Jun 2014 20:11:33 +0900 (JST) Received: from bpxc99gp.gisp.nec.co.jp ([10.38.151.141] [10.38.151.141]) by mail03.kamome.nec.co.jp with ESMTP id BT-MMP-360144; Wed, 18 Jun 2014 20:11:11 +0900 Received: from BPXM14GP.gisp.nec.co.jp ([169.254.1.238]) by BPXC13GP.gisp.nec.co.jp ([10.38.151.141]) with mapi id 14.02.0328.011; Wed, 18 Jun 2014 20:11:10 +0900 From: Hiroshi Shimamoto To: GongJinrong , "'John Joyce (joycej)'" , "dev@dpdk.org" Thread-Topic: ##freemail## RE: [dpdk-dev] Testing memnic for VM to VM transfer Thread-Index: Ac+HHDQSIPdZjtZfQguJCP7mQ7fC7wDjGP3w///VJwD//1vJkA== Date: Wed, 18 Jun 2014 11:11:09 +0000 Message-ID: <7F861DC0615E0C47A872E6F3C5FCDDBD0111B0C0@BPXM14GP.gisp.nec.co.jp> References: <7E47E681F1539348840E7A8F1E8AA02E214A68E5@xmb-aln-x09.cisco.com> <7F861DC0615E0C47A872E6F3C5FCDDBD0111A162@BPXM14GP.gisp.nec.co.jp> In-Reply-To: Accept-Language: ja-JP, en-US Content-Language: ja-JP X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.205.5.123] Content-Type: text/plain; charset="iso-2022-jp" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] ##freemail## RE: Testing memnic for VM to VM transfer X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 Jun 2014 11:11:21 -0000 Hi, > Subject: ##freemail## RE: [dpdk-dev] Testing memnic for VM to VM transfer >=20 > Hi, Hiroshi >=20 > I just start to learn DPDK and memnic, in memnic guide, you said "On > host, the shared memory must be initialized by an application using memni= c", > I am not so clear that how to initialize the share memory in host, do you > means use posix API or DPDK API to create the share memory?(it seems memn= ic > guest side use rte_mbuf to transfer data), do you have any sample code to > demo how to use memnic in host? I don't have simple MEMNIC sample to use it on host. Could you please try DPDK vSwitch and enables MEMNIC vport? DPDK vSwitch must handle packets between physical NIC port and MEMNIC vport exposed to guest with dpdk.org memnic driver. thanks, Hiroshi >=20 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Hiroshi Shimamoto > Sent: Wednesday, June 18, 2014 12:02 PM > To: John Joyce (joycej); dev@dpdk.org > Subject: Re: [dpdk-dev] Testing memnic for VM to VM transfer >=20 > Hi, >=20 > > Subject: [dpdk-dev] Testing memnic for VM to VM transfer > > > > Hi everyone: > > We are interested in testing the performance of the memnic driv= er > posted at http://dpdk.org/browse/memnic/refs/. > > We want to compare its performance compared to other techniques to > > transfer packets between the guest and the kernel, predominately for VM= to > VM transfers. > > > > We have downloaded the memnic components and have got it running in a > guest VM. > > > > The question we hope this group might be able to help with is what > > would be the best way to processes the packets in the kernel to get a V= M > to VM transfer. >=20 > I think there is no kernel code work with MEMNIC. > The recommend switching software on the host is Intel DPDK vSwitch hosted= on > 01.org and github. > https://github.com/01org/dpdk-ovs/tree/development >=20 > Intel DPDK vSwitch runs on userspace not kernel. >=20 > I introduced this mechanism to DPDK vSwitch and the guest drivers are > maintained in dpdk.org. >=20 > thanks, > Hiroshi >=20 > > > > A couple options might be possible > > > > > > 1. Common shared buffer between two VMs. With some utility/code = to > switch TX & RX rings between the two VMs. > > > > VM1 application --- memnic --- common shared memory buffer on the > > host --- memnic --- VM2 application > > > > 2. Special purpose Kernel switching module > > > > VM1 application --- memnic --- shared memory VM1 --- Kernel > > switching module --- shared memory VM2 --- memnic --- > > VM2 application > > > > 3. Existing Kernel switching module > > > > VM1 application --- memnic --- shared memory VM1 --- existing > > Kernel switching module (e.g. OVS/linux Bridge/VETh pair) > > --- shared memory VM2 --- memnic --- VM2 application > > > > Can anyone recommend which approach might be best or easiest? We woul= d > like to avoid writing much (or any) kernel code > > so if there are already any open source code or test utilities that > > provide one of these options or would be a good starting point to start > from, a pointer would be much appreciated. > > > > Thanks in advance > > > > > > John Joyce