From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from rcdn-iport-2.cisco.com (rcdn-iport-2.cisco.com [173.37.86.73]) by dpdk.org (Postfix) with ESMTP id 92B00B12F for ; Fri, 13 Jun 2014 17:28:55 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=10525; q=dns/txt; s=iport; t=1402673351; x=1403882951; h=from:to:subject:date:message-id:mime-version; bh=Ze9/Tm74FkNb1IBXrSq4uqPJCAH6qNSdxoOEVkdQn3k=; b=cS2Lt2QkyK1LkkZ4LnKKAoeT/TUeLIprAr524IwSEFYYRniLsNYAmoDf xO9VaWvVxO/eTwOyAyOhYhkpVJfc3PMCgcYrGWF5UV8eTG9yHBF521Sif OCqBaczV7szEuHvPNOeb/D0pKCHBct+637acSTwu9OISlCtiHvcyONpS6 w=; X-IronPort-Anti-Spam-Filtered: true X-IronPort-Anti-Spam-Result: AqIGAB4Ym1OtJV2b/2dsb2JhbABagkZHUlmpWgEEAQUBmACBHwGBBBZ1hAUBBC1eASpWJgEEChGIOg2jWK5RF4VciE+DY4EWBJt5khGDPIIv X-IronPort-AV: E=Sophos;i="5.01,471,1400025600"; d="scan'208,217";a="332901594" Received: from rcdn-core-4.cisco.com ([173.37.93.155]) by rcdn-iport-2.cisco.com with ESMTP; 13 Jun 2014 15:29:10 +0000 Received: from xhc-rcd-x05.cisco.com (xhc-rcd-x05.cisco.com [173.37.183.79]) by rcdn-core-4.cisco.com (8.14.5/8.14.5) with ESMTP id s5DFTA1j022345 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=FAIL) for ; Fri, 13 Jun 2014 15:29:10 GMT Received: from xmb-aln-x09.cisco.com ([169.254.4.72]) by xhc-rcd-x05.cisco.com ([173.37.183.79]) with mapi id 14.03.0123.003; Fri, 13 Jun 2014 10:29:10 -0500 From: "John Joyce (joycej)" To: "dev@dpdk.org" Thread-Topic: Testing memnic for VM to VM transfer Thread-Index: Ac+HHDQSIPdZjtZfQguJCP7mQ7fC7w== Date: Fri, 13 Jun 2014 15:29:09 +0000 Message-ID: <7E47E681F1539348840E7A8F1E8AA02E214A68E5@xmb-aln-x09.cisco.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.86.247.23] MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [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: Fri, 13 Jun 2014 15:28:56 -0000 Hi everyone: We are interested in testing the performance of the memnic driver p= osted at http://dpdk.org/browse/memnic/refs/. We want to compare its = performance compared to other techniques to transfer packets between the gu= est 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 VM to VM tran= sfer. A couple options might be possible 1. Common shared buffer between two VMs. With some utility/code to s= witch 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 mo= dule --- shared memory VM2 --- memnic --- VM2 application 3. Existing Kernel switching module VM1 application --- memnic --- shared memory VM1 --- existing Kernel swi= tching 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 would li= ke to avoid writing much (or any) kernel code so if there are already any o= pen source code or test utilities that provide one of these options or woul= d be a good starting point to start from, a pointer would be much apprecia= ted. Thanks in advance = = John Joyce