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 97B8658F6 for ; Tue, 13 Jun 2017 20:18:03 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga101.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Jun 2017 11:17:59 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.39,338,1493708400"; d="scan'208";a="867579066" Received: from fmsmsx104.amr.corp.intel.com ([10.18.124.202]) by FMSMGA003.fm.intel.com with ESMTP; 13 Jun 2017 11:17:59 -0700 Received: from fmsmsx156.amr.corp.intel.com (10.18.116.74) 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:17:58 -0700 Received: from fmsmsx113.amr.corp.intel.com ([169.254.13.162]) by fmsmsx156.amr.corp.intel.com ([169.254.13.192]) with mapi id 14.03.0319.002; Tue, 13 Jun 2017 11:17:58 -0700 From: "Wiles, Keith" To: Jay Rolette CC: "Yigit, Ferruh" , Thomas Monjalon , DPDK Thread-Topic: [dpdk-dev] [RFC] Kernel Control Path (KCP) Thread-Index: AQHS1kCLQoSPQtJRbEmdYPJ7t9WAKKINL0KAgBZsrQCAAAq7AIAABO6A Date: Tue, 13 Jun 2017 18:17:57 +0000 Message-ID: References: <20170526165228.96919-1-ferruh.yigit@intel.com> <3497879.P1UMQ6Rz4g@xps> In-Reply-To: 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: <8A2C38DC6E3BEB47953F0460CCDEC2A8@intel.com> 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:04 -0000 > On Jun 13, 2017, at 1:00 PM, Jay Rolette wrote: >=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 to >>>> 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 li= ke > to see go in regardless. Anything that helps make DPDK less "foreign" to > normal port configuration and status tools is goodness. +1 >=20 > Jay Regards, Keith