From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Wiles, Keith" <keith.wiles@intel.com>
Subject: Re: [RFC] Kernel Control Path (KCP)
Date: Tue, 13 Jun 2017 18:18:15 +0000
Message-ID: <CDEAE8F5-EF2F-499F-BDBF-ECAA8397BC65@intel.com>
References: <20170526165228.96919-1-ferruh.yigit@intel.com>
 <3497879.P1UMQ6Rz4g@xps> <d97a5127-3585-3f1d-62b6-d3460400621c@intel.com>
 <CADNuJVo0hN2YPfTHjHL36bZkZb1S+Kz1noVNfXUqAq4F3BHDwQ@mail.gmail.com>
 <3EB4FA525960D640B5BDFFD6A3D891267BA69B98@IRSMSX108.ger.corp.intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Cc: Jay Rolette <rolette@infinite.io>, "Yigit, Ferruh"
 <ferruh.yigit@intel.com>, Thomas Monjalon <thomas@monjalon.net>, DPDK
 <dev@dpdk.org>
To: "Dumitrescu, Cristian" <cristian.dumitrescu@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mga04.intel.com (mga04.intel.com [192.55.52.120])
 by dpdk.org (Postfix) with ESMTP id 59E5D7CAA
 for <dev@dpdk.org>; Tue, 13 Jun 2017 20:18:18 +0200 (CEST)
In-Reply-To: <3EB4FA525960D640B5BDFFD6A3D891267BA69B98@IRSMSX108.ger.corp.intel.com>
Content-Language: en-US
Content-ID: <AFA4E461F6B2C54289A3947A300FF3BA@intel.com>
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>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>


> On Jun 13, 2017, at 1:04 PM, Dumitrescu, Cristian <cristian.dumitrescu@in=
tel.com> 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 <ferruh.yigit@intel.com>
>> Cc: Thomas Monjalon <thomas@monjalon.net>; DPDK <dev@dpdk.org>
>> Subject: Re: [dpdk-dev] [RFC] Kernel Control Path (KCP)
>>=20
>> On Tue, Jun 13, 2017 at 12:21 PM, Ferruh Yigit <ferruh.yigit@intel.com>
>> 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