From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id EC4E929CA for ; Fri, 23 Jun 2017 14:52:52 +0200 (CEST) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 23 Jun 2017 05:52:41 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.39,378,1493708400"; d="scan'208";a="277834892" Received: from irsmsx101.ger.corp.intel.com ([163.33.3.153]) by fmsmga004.fm.intel.com with ESMTP; 23 Jun 2017 05:52:38 -0700 Received: from irsmsx102.ger.corp.intel.com ([169.254.2.211]) by IRSMSX101.ger.corp.intel.com ([169.254.1.242]) with mapi id 14.03.0319.002; Fri, 23 Jun 2017 13:47:52 +0100 From: "Van Haaren, Harry" To: Jerin Jacob , "dev@dpdk.org" CC: "Richardson, Bruce" , "hemant.agrawal@nxp.com" , "Eads, Gage" , "nipun.gupta@nxp.com" , "Vangati, Narender" , "Rao, Nikhil" , "gprathyusha@caviumnetworks.com" Thread-Topic: [dpdk-dev] [PATCH 24/33] app/testeventdev: add perf queue test Thread-Index: AQHS1+1KFGwWdsZLSUmrqLCx/LR9QaIyjNXw Date: Fri, 23 Jun 2017 12:47:50 +0000 Message-ID: References: <20170528195854.6064-1-jerin.jacob@caviumnetworks.com> <20170528195854.6064-25-jerin.jacob@caviumnetworks.com> In-Reply-To: <20170528195854.6064-25-jerin.jacob@caviumnetworks.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiYzJiNjE0MjktMTJmOC00MWYxLTg4ZjItNjU5Y2MwY2U2ZTRhIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE2LjUuOS4zIiwiVHJ1c3RlZExhYmVsSGFzaCI6InJsSVdXNHU1NGwzWmJ5WGVqU2NSTWF6UnN2eTVua2hMUWdUS2N4OFNUWGc9In0= x-ctpclassification: CTP_IC dlp-product: dlpe-windows dlp-version: 10.0.102.7 dlp-reaction: no-action x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH 24/33] app/testeventdev: add perf queue test 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: Fri, 23 Jun 2017 12:52:53 -0000 > From: Jerin Jacob [mailto:jerin.jacob@caviumnetworks.com] > Sent: Sunday, May 28, 2017 8:59 PM > To: dev@dpdk.org > Cc: Richardson, Bruce ; Van Haaren, Harry > ; hemant.agrawal@nxp.com; Eads, Gage ; > nipun.gupta@nxp.com; Vangati, Narender ; Rao,= Nikhil > ; gprathyusha@caviumnetworks.com; Jerin Jacob > > Subject: [dpdk-dev] [PATCH 24/33] app/testeventdev: add perf queue test >=20 > This is a performance test case that aims at testing the following: > 1. Measure the number of events can be processed in a second. > 2. Measure the latency to forward an event. >=20 > The perf queue test configures the eventdev with Q queues and P ports, > where Q is nb_producers * nb_stages and P is nb_workers + nb_producers. >=20 > The user can choose the number of workers, the number of producers and > number of stages through the --wlcores , --plcores and the --stlist > application command line arguments respectively. >=20 > The producer(s) injects the events to eventdev based the > first stage sched type list requested by the user through --stlist > the command line argument. >=20 > Based on the number of stages to process(selected through --stlist), > the application forwards the event to next upstream queue and > terminates when it reaches the last stage in the pipeline. > On event termination, application increments the number events > processed and print periodically in one second to get the > number of events processed in one second. We should forward events for longer than one second. From a SW PMD perspect= ive, it takes some time for caches to warm up, so running a test for 1 seco= nd isn't very representative. Suggestion of running default 5 seconds, as a= balance between consistent performance and keeping the test runs short? I'm aware of the --nb_pkts=3DX arg, this is more about solid defaults :) > When --fwd_latency command line option selected, the application > inserts the timestamp in the event on the first stage and then > on termination, it updates the number of cycles to forward > a packet. The application uses this value to compute the average > latency to a forward packet. >=20 > Example command to run perf queue test: > sudo build/app/dpdk-test-eventdev --vdev=3Devent_sw0 -- --test=3Dperf_que= ue\ > --slcore=3D1 --plcores=3D2 --wlcore=3D3 --stlist=3Dp --nb_pkts=3D10000000= 00 >=20 > Signed-off-by: Jerin Jacob With the above open; Acked-by: Harry van Haaren