From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id C26D08E59 for ; Tue, 19 Jan 2016 11:00:09 +0100 (CET) Received: from fmsmga004.fm.intel.com ([10.253.24.48]) by orsmga103.jf.intel.com with ESMTP; 19 Jan 2016 02:00:09 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,316,1449561600"; d="scan'208";a="32053775" Received: from irvmail001.ir.intel.com ([163.33.26.43]) by fmsmga004.fm.intel.com with ESMTP; 19 Jan 2016 02:00:07 -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 u0J9xo3J029283; Tue, 19 Jan 2016 09:59:51 GMT Received: from sivlogin002.ir.intel.com (localhost [127.0.0.1]) by sivlogin002.ir.intel.com with ESMTP id u0J9xoRc020732; Tue, 19 Jan 2016 09:59:50 GMT Received: (from fyigit@localhost) by sivlogin002.ir.intel.com with œ id u0J9xotg020728; Tue, 19 Jan 2016 09:59:50 GMT X-Authentication-Warning: sivlogin002.ir.intel.com: fyigit set sender to ferruh.yigit@intel.com using -f Date: Tue, 19 Jan 2016 09:59:50 +0000 From: Ferruh Yigit To: Aaron Conole Message-ID: <20160119095950.GA15736@sivlogin002.ir.intel.com> Mail-Followup-To: Aaron Conole , dev@dpdk.org References: <1452874684-12750-1-git-send-email-ferruh.yigit@intel.com> <87twmauafh.fsf@redhat.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <87twmauafh.fsf@redhat.com> User-Agent: Mutt/1.5.17 (2007-11-01) Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [RFC 0/3] 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, 19 Jan 2016 10:00:10 -0000 On Mon, Jan 18, 2016 at 11:20:02AM -0500, Aaron Conole wrote: > Ferruh Yigit writes: > > This work is to make DPDK ports more visible and to enable using common > > Linux tools to configure DPDK ports. > > This is a good goal. Only question - why use an additional kernel module > to do this? Is it _JUST_ for ethtool support? Kernel module used to create/destroy Linux net_devices, and module has a simple driver for that device which only handles control messages by passing them into userspace. To represent DPDK ports as Linux net_devices we need kernel support. > I think the other stuff > can be accomplished using netlink sockets + messages, no? Netlink sockets just used to communicate kernel-space - user-space, this is not why we need a kernel module, for example this communication is implemented in original KNI as part of FIFO. >The only > trepidation I would have with something like this is the support from > major vendors - out of tree modules are not generally supportable. Might > be good to get some of the ethtool commands as netlink messages as well, > then it is supportable with no 3rd party kernel modules. Yes, there is a out of three module problem for some distros, but unfortunately we are not able to find a solution for this case without an external kernel module. This patch is still an RFC and if we receive suggested solution without a kernel module, we can work on it together. Thanks, ferruh