From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-vk0-f52.google.com (mail-vk0-f52.google.com [209.85.213.52]) by dpdk.org (Postfix) with ESMTP id 0D0948D8F for ; Tue, 19 Jan 2016 00:48:52 +0100 (CET) Received: by mail-vk0-f52.google.com with SMTP id k1so339487078vkb.2 for ; Mon, 18 Jan 2016 15:48:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=infiniteio-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=2VbXJXsRPOgO5SGKg5kF9Gn/KzPiizlXX6VG3zOCyrc=; b=bvWoVHWUxDO7C389rszSRoK5C6SHq8j1VDAfttfF5LF17fRCC2P/0pk1WtcMrcunXC Uv5Kfsw0mByTeCWYmEEvruM1myJviAMkPqoVGE3GEqc+ZZmHDPuxHpkhBH4h5NEXDy0i d9NmpcI5feFRg+hdhrbL7eWd+hoMXwlT5FVpO3HK+PrErs6u80ShAzIYn5w58qGsE8QV M23CsW0JEwEKsZbEYSSNWFJFv55yJwcvWRJzHttnix8EHHe8A2le2dx1Y930ywYwVrvW pRuJ8FrPRoLjD84YQ1wIX/qBuJMlFq8UgwErEGJTsWXe3A9OH88KrQ7hlgcXHqGqvJSb lQ7w== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=2VbXJXsRPOgO5SGKg5kF9Gn/KzPiizlXX6VG3zOCyrc=; b=mO5Znbqm62X+qlW6A09ka1bsJYLyVzhoNrXZqu47WUacSPXtHWK9B1PfP38A1nTcsF j6XQUpMICamuH+mB8FgeGed4eHZOsn9PWr24bSnBaOa6nq1Lk0IPWGXfyV6VGpjmWd5G QcVccghIqrP00fibi0Ko1btBeMeh4szQAL3csvP8FLmUnFoj+P3vvdf9qhBleh+L0B6Z BxL5Cz53QWJddcaSmIWuRbItG5U/QNXC9rERnffi37aFY+NgezBhYOfBav9CXWakHOe/ K/VOlH3/mAHyqsDik4AfZUHvsmb1AvY800mpt5z/wnUNTBy5uFkwqHpfV6nmFPXKHHU/ 0I0A== X-Gm-Message-State: ALoCoQl22AxJymoYXEuQEq20C8A6rGxeLjl8uJXql0Y6HWvXo3vSJmQMJtOk44vO17HQqIbJkZcdPy5BRLFALdQUa/vUHasUOA== MIME-Version: 1.0 X-Received: by 10.31.156.129 with SMTP id f123mr18633579vke.40.1453160931408; Mon, 18 Jan 2016 15:48:51 -0800 (PST) Received: by 10.103.8.69 with HTTP; Mon, 18 Jan 2016 15:48:51 -0800 (PST) In-Reply-To: <20160118151230.194a95c6@xeon-e3> References: <1452874684-12750-1-git-send-email-ferruh.yigit@intel.com> <20160118151230.194a95c6@xeon-e3> Date: Mon, 18 Jan 2016 17:48:51 -0600 Message-ID: From: Jay Rolette To: Stephen Hemminger Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: DPDK 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: Mon, 18 Jan 2016 23:48:52 -0000 On Mon, Jan 18, 2016 at 5:12 PM, Stephen Hemminger < stephen@networkplumber.org> wrote: > On Fri, 15 Jan 2016 16:18:01 +0000 > Ferruh Yigit wrote: > > > 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. > > I actually would like KNI to die and be replaced by something generic. > Right now with KNI it is driver and hardware specific. It is almost as if > there > are three drivers for ixgbe, the Linux driver, the DPDK driver, and the > KNI driver. > Any ideas about what that would look like? Having the ability to send traffic to/from DPDK-owned ports from control plane applications that live outside of (and are ignorant of) DPDK is a platform requirement for our product. I'm assuming that isn't uncommon, but that could just be the nature of the types of products I've built over the years. That said, I'd love there to be something that performs better and plays nicer with the system than KNI. Jay