From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 59E5D7CAA for ; Tue, 13 Jun 2017 20:18:18 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga104.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Jun 2017 11:18:17 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.39,338,1493708400"; d="scan'208";a="867579147" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by FMSMGA003.fm.intel.com with ESMTP; 13 Jun 2017 11:18:17 -0700 Received: from fmsmsx119.amr.corp.intel.com (10.18.124.207) by fmsmsx104.amr.corp.intel.com (10.18.124.202) with Microsoft SMTP Server (TLS) id 14.3.319.2; Tue, 13 Jun 2017 11:18:17 -0700 Received: from fmsmsx113.amr.corp.intel.com ([169.254.13.162]) by FMSMSX119.amr.corp.intel.com ([169.254.14.198]) with mapi id 14.03.0319.002; Tue, 13 Jun 2017 11:18:16 -0700 From: "Wiles, Keith" To: "Dumitrescu, Cristian" CC: Jay Rolette , "Yigit, Ferruh" , Thomas Monjalon , DPDK Thread-Topic: [dpdk-dev] [RFC] Kernel Control Path (KCP) Thread-Index: AQHS1kCLQoSPQtJRbEmdYPJ7t9WAKKINL0KAgBZsrQCAAAq7AIAAASaAgAAD3wA= Date: Tue, 13 Jun 2017 18:18:15 +0000 Message-ID: References: <20170526165228.96919-1-ferruh.yigit@intel.com> <3497879.P1UMQ6Rz4g@xps> <3EB4FA525960D640B5BDFFD6A3D891267BA69B98@IRSMSX108.ger.corp.intel.com> In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D891267BA69B98@IRSMSX108.ger.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [10.252.134.185] Content-Type: text/plain; charset="us-ascii" Content-ID: Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [RFC] Kernel Control Path (KCP) 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: Tue, 13 Jun 2017 18:18:18 -0000 > On Jun 13, 2017, at 1:04 PM, Dumitrescu, Cristian wrote: >=20 >=20 >=20 >> -----Original Message----- >> From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Jay Rolette >> Sent: Tuesday, June 13, 2017 7:00 PM >> To: Yigit, Ferruh >> Cc: Thomas Monjalon ; DPDK >> Subject: Re: [dpdk-dev] [RFC] Kernel Control Path (KCP) >>=20 >> On Tue, Jun 13, 2017 at 12:21 PM, Ferruh Yigit >> wrote: >>=20 >>> On 5/30/2017 11:55 AM, Thomas Monjalon wrote: >>>> 26/05/2017 18:52, Ferruh Yigit: >>>>> We are looking for re-sending [1] the Kernel Control Path (KCP) >>>>> with some updates [2]. >>>>>=20 >>>>> Mainly this is an usability improvement for DPDK. >>>>>=20 >>>>> And a quick reminder about what KCP is: >>>>>=20 >>>>> "KCP is Linux virtual network interface that can control DPDK ports". >>>>>=20 >>>>> So DPDK interfaces, somehow will be visible and it will be possible t= o >>>>> use common Linux tools on DPDK interfaces. >>>>=20 >>>> Reminder: the Mellanox PMDs live with their upstream kernel modules, >>>> allowing such features. >>>>=20 >>>> The best model would be to have control path in kernel for every PMDs. >>>=20 >>> That is the intention with this feature. >>>=20 >>>>=20 >>>> Anyway, do you think KCP (or NCI) could be upstreamed in any way? >>>=20 >>> Unfortunately I believe the answer is same, it may not be possible to >>> upsteam this kernel module. Should this fact block the feature? >>>=20 >>=20 >> Upstream is better, but KCP is a nice quality-of-life feature that I'd l= ike >> to see go in regardless. Anything that helps make DPDK less "foreign" to >> normal port configuration and status tools is goodness. >>=20 >> Jay >=20 > +1 +1 >=20 > Let's not block this feature based on Linux kernel upstream reasons. Regards, Keith