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 82EA85320 for ; Tue, 15 Mar 2016 01:00:47 +0100 (CET) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga101.fm.intel.com with ESMTP; 14 Mar 2016 17:00:46 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,337,1455004800"; d="scan'208";a="937085195" Received: from unknown (HELO [10.252.26.94]) ([10.252.26.94]) by fmsmga002.fm.intel.com with ESMTP; 14 Mar 2016 17:00:44 -0700 To: Jay Rolette References: <1456846920-28770-1-git-send-email-ferruh.yigit@intel.com> <1457523689-6223-1-git-send-email-ferruh.yigit@intel.com> <56E6D956.8050809@intel.com> Cc: DPDK , David Marchand , Helin Zhang , Remy Horton From: Ferruh Yigit Message-ID: <56E750AB.3040707@intel.com> Date: Tue, 15 Mar 2016 00:00:43 +0000 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] [PATCH v5 0/4] Use common Linux tools to control DPDK ports X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 15 Mar 2016 00:00:48 -0000 On 3/14/2016 5:40 PM, Jay Rolette wrote: > Is there some technical reason or is it just the push-back you are > getting from some of the maintainers? > The majority of the discussion on the list was based on not having kernel modules, which cloud the desired technical discussion. As a result of the opposition, we will give a try to upstreaming and I will be able to use some of my time to work on this. If KCP can be upstreamed, this is good for everybody, if not I hope we can discuss again in community the future of the feature. And during this process, userspace counterpart in DPDK will be missing, and kernel part will be in a form of patch for head of latest kernel, so not sure how community will be able to test this. > I chimed in on one of the other threads already, but I'm extremely > disappointed that usability and serviceability improvements to existing > DPDK capabilities (KNI) are getting blocked like this. > > For companies building network appliances based on DPDK, having a kernel > module that isn't in the tree just isn't that big of a deal. Long term > goals for getting this upstream are great, but why not take advantage of > incremental improvements in the meantime? > > Jay > > On Mon, Mar 14, 2016 at 10:31 AM, Ferruh Yigit > wrote: > > 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. > >