From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id EFD621F5 for ; Mon, 22 Feb 2016 15:00:07 +0100 (CET) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by fmsmga104.fm.intel.com with ESMTP; 22 Feb 2016 06:00:07 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,484,1449561600"; d="scan'208";a="657139063" Received: from irvmail001.ir.intel.com ([163.33.26.43]) by FMSMGA003.fm.intel.com with ESMTP; 22 Feb 2016 06:00:05 -0800 Received: from sivlogin002.ir.intel.com (sivlogin002.ir.intel.com [10.237.217.37]) by irvmail001.ir.intel.com (8.14.3/8.13.6/MailSET/Hub) with ESMTP id u1ME04Mv010427; Mon, 22 Feb 2016 14:00:05 GMT Received: from sivlogin002.ir.intel.com (localhost [127.0.0.1]) by sivlogin002.ir.intel.com with ESMTP id u1ME04TN014927; Mon, 22 Feb 2016 14:00:04 GMT Received: (from fyigit@localhost) by sivlogin002.ir.intel.com with œ id u1ME03vv014923; Mon, 22 Feb 2016 14:00:03 GMT X-Authentication-Warning: sivlogin002.ir.intel.com: fyigit set sender to ferruh.yigit@intel.com using -f Date: Mon, 22 Feb 2016 14:00:02 +0000 From: Ferruh Yigit To: Stephen Hemminger Message-ID: <20160222140002.GA10693@sivlogin002.ir.intel.com> Mail-Followup-To: Stephen Hemminger , Helin Zhang , dev@dpdk.org, aconole@redhat.com References: <20160220170708.37d0db29@xeon-e3> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20160220170708.37d0db29@xeon-e3> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: dev@dpdk.org Subject: Re: [dpdk-dev] KNI - issues 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: Mon, 22 Feb 2016 14:00:08 -0000 On Sat, Feb 20, 2016 at 05:07:08PM -0800, Stephen Hemminger wrote: > Is anyone working on making KNI conform to current kernel best practices > and attempt to get it upstream? After 2 minute code review I already > see lots and lots of things that need work. Hi Stephen, I am working on not KNI, but on KNI enhancements: KCP and KDP. KCP: Kernel Control Path http://dpdk.org/dev/patchwork/patch/10481/ KDP: Kernel Data Path http://dpdk.org/dev/patchwork/patch/10667/ Both are based on KNI, and KNI responsibilities split into these two modules, if these cover customer requirements, they can replace current KNI. KCP: Common Linux tools support without kernel drivers inside KNI required. KDP: Slow data path communication as PMD, supports both KNI FIFO and tap device. And in mail list, problems of using out-of-tree kernel module mentioned a few times, I can take over the task to submit a generic solution to Linux upstream, as a follow up to KCP and KDP tasks, but I need some kind of experts feedback about feasibility of this work. That is why I have sent a call to mail list about this issue: http://dpdk.org/ml/archives/dev/2016-February/033279.html Thanks to Aaron, he provided his support. I would like to get your idea too. Specially I am planning to use rtnetlink and as iproute2 maintainer I believe you already have some answers I am looking for. Thanks, ferruh