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 D5AD81F5 for ; Thu, 25 Sep 2014 01:48:37 +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 s8ONsk8k005479; Thu, 25 Sep 2014 08:54:46 +0900 (JST) Received: from mailsv3.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 s8ONsjC19257; Thu, 25 Sep 2014 08:54:45 +0900 (JST) Received: from mail02.kamome.nec.co.jp (mail02.kamome.nec.co.jp [10.25.43.5]) by mailsv3.nec.co.jp (8.13.8/8.13.4) with ESMTP id s8ONsjuZ016169; Thu, 25 Sep 2014 08:54:45 +0900 (JST) Received: from bpxc99gp.gisp.nec.co.jp ([10.38.151.143] [10.38.151.143]) by mail01b.kamome.nec.co.jp with ESMTP id BT-MMP-2085009; Thu, 25 Sep 2014 08:54:20 +0900 Received: from BPXM14GP.gisp.nec.co.jp ([169.254.1.136]) by BPXC15GP.gisp.nec.co.jp ([10.38.151.143]) with mapi id 14.03.0174.002; Thu, 25 Sep 2014 08:54:19 +0900 From: Hiroshi Shimamoto To: Thomas Monjalon Thread-Topic: [dpdk-dev] [memnic PATCH 1/7] guest: memnic-tester: PMD benchmark in guest Thread-Index: AQHP2AnCryvEpEbb2EK6BvbR2e3p6ZwQ75rg Date: Wed, 24 Sep 2014 23:54:19 +0000 Message-ID: <7F861DC0615E0C47A872E6F3C5FCDDBD02AD9DD6@BPXM14GP.gisp.nec.co.jp> References: <7F861DC0615E0C47A872E6F3C5FCDDBD011A98C5@BPXM14GP.gisp.nec.co.jp> <9049135.zKavqy3ols@xps13> In-Reply-To: <9049135.zKavqy3ols@xps13> 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 Cc: "dev@dpdk.org" , Hayato Momma Subject: Re: [dpdk-dev] [memnic PATCH 1/7] guest: memnic-tester: PMD benchmark in guest 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, 24 Sep 2014 23:48:38 -0000 Hi, > Subject: Re: [dpdk-dev] [memnic PATCH 1/7] guest: memnic-tester: PMD benc= hmark in guest >=20 > Hi Hiroshi, >=20 > 2014-09-11 07:46, Hiroshi Shimamoto: > > master |<- put packets ->| |<- get packets ->| > > slave | |<- rx packets ->|<- tx packets ->| | > > |<----------------- set ----------------->| > > > > Measuring how many sets in the certain period, that represents > > the MEMNIC PMD performance. The master workload must be very low. >=20 > Sorry, I don't really understand this diagram and the associated explanat= ion. > Could you try to reword it? sure, will make more understandable description. Could you please help me to do that? The purpose of this program is measuring the performance of MEMNIC PMD itse= lf. It means that we'd like to know how much the PMD takes in rx and tx API. The program does rx and tx in the slave thread and the PMD performance coul= d be measured how much packets are handled in certain period. By the way we need to fill and clear MEMNIC packet buffer for enabling to work the PMD rx= /tx in the slave thread. Then, I made the master thread which fills and clears MEMNIC packet buffer in the lightest way, and it should be with the least j= itter. If we generate a real packet out of VM, that may cause increasing jitter outside of the MEMNIC PMD, it means we will not see the precise performance of MEMNIC PMD itself. Can you see the concept of this benchmark with the above? thanks, Hiroshi >=20 > Thanks > -- > Thomas