From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id EE01491D0 for ; Sat, 5 Dec 2015 13:06:59 +0100 (CET) Received: from orsmga001.jf.intel.com ([10.7.209.18]) by fmsmga101.fm.intel.com with ESMTP; 05 Dec 2015 04:06:59 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.20,384,1444719600"; d="scan'208";a="834870070" Received: from irsmsx153.ger.corp.intel.com ([163.33.192.75]) by orsmga001.jf.intel.com with ESMTP; 05 Dec 2015 04:06:57 -0800 Received: from irsmsx156.ger.corp.intel.com (10.108.20.68) by IRSMSX153.ger.corp.intel.com (163.33.192.75) with Microsoft SMTP Server (TLS) id 14.3.248.2; Sat, 5 Dec 2015 12:06:56 +0000 Received: from irsmsx103.ger.corp.intel.com ([169.254.3.13]) by IRSMSX156.ger.corp.intel.com ([169.254.3.110]) with mapi id 14.03.0248.002; Sat, 5 Dec 2015 12:06:56 +0000 From: "Betts, Ian" To: Thomas Monjalon , Stephen Hemminger Thread-Topic: [dpdk-dev] [PATCH v8 0/4] examples: add performance-thread Thread-Index: AQHRLn9lrOhOVTIF3UavZvcpaBLUvp67H02AgAAIVICAASAw4A== Date: Sat, 5 Dec 2015 12:06:56 +0000 Message-ID: <877C1F8553E92F43898365570816082F35C0BDF7@IRSMSX103.ger.corp.intel.com> References: <1449159683-7092-3-git-send-email-ian.betts@intel.com> <1449225265-14480-1-git-send-email-ian.betts@intel.com> <20151204100359.6b966aea@xeon-e3> <1850494.rdblc2vbpm@xps13> In-Reply-To: <1850494.rdblc2vbpm@xps13> Accept-Language: en-IE, en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-inteldataclassification: CTP_PUBLIC x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsIiwiaWQiOiI1ODcwMWU5Yi05MjU4LTRmNTQtOTEzYS1hMTE4NDcxN2E1MDkiLCJwcm9wcyI6W3sibiI6IkludGVsRGF0YUNsYXNzaWZpY2F0aW9uIiwidmFscyI6W3sidmFsdWUiOiJDVFBfUFVCTElDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjQuMTAuMTkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiXC9DTWI5TVVScUlEcjUzNTZIdnUzdnRzeEtGWmNCUWVRb3Vxc1h2SUtySkk9In0= x-originating-ip: [163.33.239.181] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH v8 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: Sat, 05 Dec 2015 12:07:00 -0000 -----Original Message----- From: Thomas Monjalon [mailto:thomas.monjalon@6wind.com]=20 Sent: Friday, December 4, 2015 6:34 PM To: Stephen Hemminger Cc: dev@dpdk.org; Betts, Ian Subject: Re: [dpdk-dev] [PATCH v8 0/4] examples: add performance-thread 2015-12-04 10:03, Stephen Hemminger: > Looks useful, but this needs more discussion. >=20 > Maybe it should be a separate library not tied into DPDK so it gets=20 > wider use and testing? Also what are the limitations? > What if an lthread did a system call? What about interaction with=20 > rte_poll? >=20 > Earlier attempts at lightweight threading (fibers) would be worth=20 > looking into. http://c2.com/cgi/wiki?CooperativeThreading > Intel Thread Building Blocks > IBM NGPT (now defunct) >=20 > There lots of hidden gotcha's here, like preemption (or not), and=20 > limitations on interactions with other libraries. >=20 > Intel may have some milestone to get it into DPDK 2.2 but really this=20 > seems too late... >>>Yes, sure it is too late to have enough discussions in 2.2 timeframe. Just to understand what we mean by too late... The original RFC was issued on 2nd September. Thus there have been some three months available for discussion, and for people to raise any questions or concerns. =20 The first patch was available on 30th September, and a number of subsequent patch versions have been issued, =20 meaning the code has been available for review for two months. As mentioned in the reply to Stephen, there has been no adverse feedback during this period. /Ian