From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from tyo202.gate.nec.co.jp (TYO202.gate.nec.co.jp [210.143.35.52]) by dpdk.org (Postfix) with ESMTP id C6B366A69 for ; Wed, 18 Jun 2014 06:02:33 +0200 (CEST) Received: from mailgate3.nec.co.jp ([10.7.69.193]) by tyo202.gate.nec.co.jp (8.13.8/8.13.4) with ESMTP id s5I42i7t015847; Wed, 18 Jun 2014 13:02:44 +0900 (JST) Received: from mailsv3.nec.co.jp (imss61.nec.co.jp [10.7.69.156]) by mailgate3.nec.co.jp (8.11.7/3.7W-MAILGATE-NEC) with ESMTP id s5I42id00917; Wed, 18 Jun 2014 13:02:44 +0900 (JST) Received: from mail01b.kamome.nec.co.jp (mail01b.kamome.nec.co.jp [10.25.43.2]) by mailsv3.nec.co.jp (8.13.8/8.13.4) with ESMTP id s5I42ixP005613; Wed, 18 Jun 2014 13:02:44 +0900 (JST) Received: from bpxc99gp.gisp.nec.co.jp ([10.38.151.141] [10.38.151.141]) by mail02.kamome.nec.co.jp with ESMTP id BT-MMP-344842; Wed, 18 Jun 2014 13:02:21 +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 13:02:20 +0900 From: Hiroshi Shimamoto To: "John Joyce (joycej)" , "dev@dpdk.org" Thread-Topic: Testing memnic for VM to VM transfer Thread-Index: Ac+HHDQSIPdZjtZfQguJCP7mQ7fC7wDjGP3w Date: Wed, 18 Jun 2014 04:02:20 +0000 Message-ID: <7F861DC0615E0C47A872E6F3C5FCDDBD0111A162@BPXM14GP.gisp.nec.co.jp> References: <7E47E681F1539348840E7A8F1E8AA02E214A68E5@xmb-aln-x09.cisco.com> In-Reply-To: <7E47E681F1539348840E7A8F1E8AA02E214A68E5@xmb-aln-x09.cisco.com> 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] 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 04:02:34 -0000 Hi, > Subject: [dpdk-dev] Testing memnic for VM to VM transfer >=20 > Hi everyone: > We are interested in testing the performance of the memnic driver= posted at http://dpdk.org/browse/memnic/refs/. > We want to compare its performance compared to other techniques to transf= er packets between the guest and the kernel, > predominately for VM to VM transfers. >=20 > We have downloaded the memnic components and have got it running in a gue= st VM. >=20 > 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 VM to VM transfer. I think there is no kernel code work with MEMNIC. The recommend switching software on the host is Intel DPDK vSwitch hosted o= n 01.org and github. https://github.com/01org/dpdk-ovs/tree/development Intel DPDK vSwitch runs on userspace not kernel. I introduced this mechanism to DPDK vSwitch and the guest drivers are maint= ained in dpdk.org. thanks, Hiroshi >=20 > A couple options might be possible >=20 >=20 > 1. Common shared buffer between two VMs. With some utility/code to= switch TX & RX rings between the two VMs. >=20 > VM1 application --- memnic --- common shared memory buffer on the host = --- memnic --- VM2 application >=20 > 2. Special purpose Kernel switching module >=20 > VM1 application --- memnic --- shared memory VM1 --- Kernel switching = module --- shared memory VM2 --- memnic --- > VM2 application >=20 > 3. Existing Kernel switching module >=20 > VM1 application --- memnic --- shared memory VM1 --- existing Kernel s= witching module (e.g. OVS/linux Bridge/VETh pair) > --- shared memory VM2 --- memnic --- VM2 application >=20 > Can anyone recommend which approach might be best or easiest? We would = like to avoid writing much (or any) kernel code > so if there are already any open source code or test utilities that provi= de one of these options or would be a good starting > point to start from, a pointer would be much appreciated. >=20 > Thanks in advance >=20 >=20 > John Joyce