From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: [RFC] Kernel Control Path (KCP)
Date: Mon, 29 May 2017 10:26:40 +0100
Message-ID: <20170529092640.GA32120@bricha3-MOBL3.ger.corp.intel.com>
References: <20170526165228.96919-1-ferruh.yigit@intel.com>
 <1A6BF4F7-AD63-4888-99B1-796B31C274DB@intel.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: "Yigit, Ferruh" <ferruh.yigit@intel.com>, DPDK <dev@dpdk.org>,
 "Walker, Benjamin" <benjamin.walker@intel.com>
To: "Wiles, Keith" <keith.wiles@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20])
 by dpdk.org (Postfix) with ESMTP id 4E49A374C
 for <dev@dpdk.org>; Mon, 29 May 2017 11:26:49 +0200 (CEST)
Content-Disposition: inline
In-Reply-To: <1A6BF4F7-AD63-4888-99B1-796B31C274DB@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 Sun, May 28, 2017 at 04:55:11PM +0000, Wiles, Keith wrote:
> 
> > On May 26, 2017, at 11:52 AM, Ferruh Yigit <ferruh.yigit@intel.com> wrote:
> > 
> > We are looking for re-sending [1] the Kernel Control Path (KCP)
> > with some updates [2].
> > 
> > Mainly this is an usability improvement for DPDK.
> > 
> > And a quick reminder about what KCP is:
> > 
> > "KCP is Linux virtual network interface that can control DPDK ports".
> > 
> > So DPDK interfaces, somehow will be visible and it will be possible to
> > use common Linux tools on DPDK interfaces.
> > 
> > This work can be done in multiple steps:
> > 
> > - At first step virtual interfaces can be read-only, and can be used
> >  to get stats / information from DPDK ports.
> > 
> > - Second step can be controlling the DPDK interfaces in a common way
> >  like Linux interfaces.
> > 
> > It is good to remind that KCP is only for control path, and no data
> > traffic will be available on those interfaces, meaning not able to use
> > tcpdump or similar tools on those interfaces.
> > 
> > I would like to hear about comments, requirements and objection about
> > the idea?
> > 
> > Also the name "Kernel Control Path" can be too broad, I am open to a
> > name change, any comments on naming is welcome.
> 
> Using kernel in the name is not very useful, but netlink is the real part that makes sense.
> 
> How about one of these:
> - DNI = DPDK Netlink Interface
> - DNC = DPDK Netlink Control
> - NCI = Netlink Control Interface
> 
I like that last one, NCI. [It's also pronouncable as "nicky", too]

/Bruce