From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by dpdk.org (Postfix) with ESMTP id 4E49A374C for ; Mon, 29 May 2017 11:26:49 +0200 (CEST) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga101.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 29 May 2017 02:26:43 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.38,413,1491289200"; d="scan'208";a="267623071" Received: from bricha3-mobl3.ger.corp.intel.com ([10.237.221.42]) by fmsmga004.fm.intel.com with SMTP; 29 May 2017 02:26:41 -0700 Received: by (sSMTP sendmail emulation); Mon, 29 May 2017 10:26:40 +0100 Date: Mon, 29 May 2017 10:26:40 +0100 From: Bruce Richardson To: "Wiles, Keith" Cc: "Yigit, Ferruh" , DPDK , "Walker, Benjamin" 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 Content-Disposition: inline In-Reply-To: <1A6BF4F7-AD63-4888-99B1-796B31C274DB@intel.com> Organization: Intel Research and =?iso-8859-1?Q?De=ACvel?= =?iso-8859-1?Q?opment?= Ireland Ltd. User-Agent: Mutt/1.8.1 (2017-04-11) 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: Mon, 29 May 2017 09:26:50 -0000 On Sun, May 28, 2017 at 04:55:11PM +0000, Wiles, Keith wrote: > > > On May 26, 2017, at 11:52 AM, Ferruh Yigit 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