From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <harry.van.haaren@intel.com> Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 160EB995E for <dev@dpdk.org>; Thu, 25 May 2017 15:27:59 +0200 (CEST) Received: from orsmga004.jf.intel.com ([10.7.209.38]) by fmsmga102.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 25 May 2017 06:27:58 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.38,391,1491289200"; d="scan'208";a="91366968" Received: from irsmsx108.ger.corp.intel.com ([163.33.3.3]) by orsmga004.jf.intel.com with ESMTP; 25 May 2017 06:27:57 -0700 Received: from irsmsx102.ger.corp.intel.com ([169.254.2.153]) by IRSMSX108.ger.corp.intel.com ([169.254.11.239]) with mapi id 14.03.0319.002; Thu, 25 May 2017 14:27:49 +0100 From: "Van Haaren, Harry" <harry.van.haaren@intel.com> To: "Ananyev, Konstantin" <konstantin.ananyev@intel.com>, "Richardson, Bruce" <bruce.richardson@intel.com> CC: "dev@dpdk.org" <dev@dpdk.org>, Thomas Monjalon <thomas@monjalon.net>, Jerin Jacob <jerin.jacob@caviumnetworks.com> Thread-Topic: [dpdk-dev] [RFC] service core concept header implementation Thread-Index: AQHSxACR6paJvJqAzkOCT2rlM3T1nqH4ftMAgAAC3YCAAA26gIAMm8kg Date: Thu, 25 May 2017 13:27:49 +0000 Message-ID: <E923DB57A917B54B9182A2E928D00FA612A3C594@IRSMSX102.ger.corp.intel.com> References: <1493810961-139469-1-git-send-email-harry.van.haaren@intel.com> <1493810961-139469-2-git-send-email-harry.van.haaren@intel.com> <2601191342CEEE43887BDE71AB9772583FAF750C@IRSMSX109.ger.corp.intel.com> <20170517125806.GA14804@bricha3-MOBL3.ger.corp.intel.com> <2601191342CEEE43887BDE71AB9772583FAF76D7@IRSMSX109.ger.corp.intel.com> In-Reply-To: <2601191342CEEE43887BDE71AB9772583FAF76D7@IRSMSX109.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiODg1MGNlN2UtNzQzZi00YTM4LTk4OTctMGQzMDU1NzQ0YzQ2IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX0lDIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE1LjkuNi42IiwiVHJ1c3RlZExhYmVsSGFzaCI6IkdWR1daUTVaNndHRUQ3NUVRbmRhTTdXSitLWVhqMDdxbDBhOUN3aDRIdU09In0= x-ctpclassification: CTP_IC dlp-product: dlpe-windows dlp-version: 10.0.102.7 dlp-reaction: no-action 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] [RFC] service core concept header implementation X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Thu, 25 May 2017 13:28:00 -0000 Hi All, <snip> Service Cores RFC, more details and discussion </snip> > Though I think both PMD/core libraries and app layer might be interested= in that: i.e. > app might also have some background processing tasks, that might need to = be run > on several cores (or core slices). Thanks everybody for the input on the RFC - appreciated! From an applicatio= n point-of-view, I see merit in Konstantin's suggestions for the API, over = the RFC I sent previously. I will re-work the API taking inspiration from b= oth APIs and send an RFCv2, you'll be on CC :) Cheers, -Harry