From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ferruh Yigit Subject: Re: [RFC 0/2] slow data path communication between DPDK port and Linux Date: Fri, 22 Jan 2016 16:56:15 +0000 Message-ID: <20160122165615.GA31579@sivlogin002.ir.intel.com> References: <1453478442-23000-1-git-send-email-ferruh.yigit@intel.com> <1881890.o9IDb9bZGc@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: dev@dpdk.org To: Thomas Monjalon Return-path: Received: from mga01.intel.com (mga01.intel.com [192.55.52.88]) by dpdk.org (Postfix) with ESMTP id 14BE08F9B for ; Fri, 22 Jan 2016 17:56:18 +0100 (CET) Content-Disposition: inline In-Reply-To: <1881890.o9IDb9bZGc@xps13> 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 Fri, Jan 22, 2016 at 05:31:45PM +0100, Thomas Monjalon wrote: > Hi Ferruh, > > Not commenting the implementation, just the method. > > 2016-01-22 16:00, Ferruh Yigit: > > This is slow data path communication implementation based on existing KNI. > > Difference is: librte_kni converted into a PMD, kdp kernel module is almost > > same except all control path functionality removed and some simplification done. > > Is there a chance to submit such kernel module on LKML instead of DPDK? > We should avoid maintaining some out-of-tree modules. The ones I have sent are not generic enough to be in Linux tree. We already maintain kni kernel module, these patches are part of effort to make kni more maintainable, by separation of concerns, removing network drivers from it, and simplifying some of code. For this patch set, tun/tap interface can be alternative, and it looks like it removes out-of-tree kernel module requirement, unless people want current FIFO implementation because of better performance. For control path, unfortunately I am not aware of any solution without out-of-tree kernel module support. Thanks, ferruh