From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 431C94A63 for ; Thu, 3 Dec 2015 10:48:31 +0100 (CET) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga101.jf.intel.com with ESMTP; 03 Dec 2015 01:48:30 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,377,1444719600"; d="scan'208";a="863734041" Received: from irsmsx106.ger.corp.intel.com ([163.33.3.31]) by orsmga002.jf.intel.com with ESMTP; 03 Dec 2015 01:48:29 -0800 Received: from irsmsx102.ger.corp.intel.com ([169.254.2.251]) by IRSMSX106.ger.corp.intel.com ([169.254.8.228]) with mapi id 14.03.0248.002; Thu, 3 Dec 2015 09:48:28 +0000 From: "Kulasek, TomaszX" To: "Betts, Ian" , "dev@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH v5 0/4] examples: add performance-thread Thread-Index: AQHRLa1F9Z74hsuMq02JY0/c64UWsZ65A5gQ Date: Thu, 3 Dec 2015 09:48:27 +0000 Message-ID: <3042915272161B4EB253DA4D77EB373A14E21E9F@IRSMSX102.ger.corp.intel.com> References: <1449134905-28261-1-git-send-email-ian.betts@intel.com> In-Reply-To: <1449134905-28261-1-git-send-email-ian.betts@intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH v5 0/4] examples: add performance-thread 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: Thu, 03 Dec 2015 09:48:31 -0000 > -----Original Message----- > From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of ibetts > Sent: Thursday, December 3, 2015 10:28 > To: dev@dpdk.org > Cc: Betts, Ian > Subject: [dpdk-dev] [PATCH v5 0/4] examples: add performance-thread >=20 > From: Ian Betts >=20 > This patchset comprises a layer 3 forwarding derivative intended to > facilitate characterization of performance with different threading > models, specifically:- >=20 > 1. EAL threads running on different physical cores 2. EAL threads > running on the same physical core 3. Lightweight threads running in an > EAL thread >=20 > Purpose and justification >=20 > Since dpdk 2.0 it has been possible to assign multiple EAL threads to a > physical core ( case 2 above ). > Currently no example application has focused on demonstrating the > performance constraints of differing threading models. >=20 > Whilst purpose built applications that fully comprehend the DPDK single > threaded programming model will always yield superior performance, the > desire to preserve ROI in legacy code written for multithreaded > operating environments makes lightweight threads (case 3 above) worthy > of consideration. >=20 > As well as aiding with legacy code reuse, it is anticipated that > lightweight threads will make it possible to scale a multithreaded > application with fine granularity allowing an application to more > easily take advantage of headroom on EAL cores, or conversely occupy > more cores, as dictated by system load. >=20 > To explore performance with lightweight threads a simple cooperative > scheduler subsystem is being included in this example application. > If the expected benefits and use cases prove to be of value, it is > anticipated that this lightweight thread subsystem would become a > library in some future DPDK release. >=20 >=20 > Changes in this version > * None > Idenitical with the V4 patchset, which comprised 2 patches. > V5 is divided into more 5 patches. >=20 >=20 > Ian Betts (4): > doc: add sample application guide for performance-thread > examples: add lthread subsystem for performance-thread > examples: add l3fwd-thread example in performance-thread > examples: add pthread_shim example to performance thread >=20 > -- > 2.1.4 Series Acked-by: Tomasz Kulasek