From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [PATCH v5 0/4] Use common Linux tools to control DPDK ports Date: Mon, 14 Mar 2016 15:31:34 +0000 Message-ID: <56E6D956.8050809@intel.com> References: <1456846920-28770-1-git-send-email-ferruh.yigit@intel.com> <1457523689-6223-1-git-send-email-ferruh.yigit@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: David Marchand , Helin Zhang , Remy Horton To: dev@dpdk.org Return-path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id C90202C6C for ; Mon, 14 Mar 2016 16:31:38 +0100 (CET) In-Reply-To: <1457523689-6223-1-git-send-email-ferruh.yigit@intel.com> List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 3/9/2016 11:41 AM, Ferruh Yigit wrote: > This patch sent to keep record of latest status of the work. > > > This work is to make DPDK ports more visible and to enable using common > Linux tools to configure DPDK ports. > > Patch is based on KNI but contains only control functionality of it, > also this patch does not include any Linux kernel network driver as > part of it. > > Basically with the help of a kernel module (KCP), virtual Linux network > interfaces named as "dpdk$" are created per DPDK port, control messages > sent to these virtual interfaces are forwarded to DPDK, and response > sent back to Linux application. > > Virtual interfaces created when DPDK application started and destroyed > automatically when DPDK application terminated. > > Communication between kernel-space and DPDK done using netlink socket. > > In long term this patch intends to replace the KNI and KNI will be > depreciated. > Self-NACK: Will work on netdev to upstream this.