From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga11.intel.com (mga11.intel.com [192.55.52.93]) by dpdk.org (Postfix) with ESMTP id 96D14AFCD for ; Thu, 22 May 2014 15:24:09 +0200 (CEST) Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by fmsmga102.fm.intel.com with ESMTP; 22 May 2014 06:24:18 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="4.98,887,1392192000"; d="scan'208";a="536027385" Received: from irsmsx103.ger.corp.intel.com ([163.33.3.157]) by fmsmga001.fm.intel.com with ESMTP; 22 May 2014 06:24:17 -0700 Received: from irsmsx153.ger.corp.intel.com (163.33.192.75) by IRSMSX103.ger.corp.intel.com (163.33.3.157) with Microsoft SMTP Server (TLS) id 14.3.123.3; Thu, 22 May 2014 14:24:17 +0100 Received: from irsmsx101.ger.corp.intel.com ([169.254.1.249]) by IRSMSX153.ger.corp.intel.com ([169.254.9.50]) with mapi id 14.03.0123.003; Thu, 22 May 2014 14:24:13 +0100 From: "Burakov, Anatoly" To: Thomas Monjalon Thread-Topic: [dpdk-dev] [PATCH v2 13/16] Removed PCI ID table from igb_uio Thread-Index: AQHPc3pXGKll1Pfl2UuXQHOBRlkCc5tMh56AgAAR33A= Date: Thu, 22 May 2014 13:24:13 +0000 Message-ID: References: <1400514709-24087-14-git-send-email-anatoly.burakov@intel.com> <1444994.s4JW68cLD9@xps13> In-Reply-To: <1444994.s4JW68cLD9@xps13> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-originating-ip: [163.33.239.182] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH v2 13/16] Removed PCI ID table from igb_uio 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: Thu, 22 May 2014 13:24:10 -0000 Hi Thomas, > I wonder if we could replace igb_uio by uio_pci_generic? Can it do DMA or IOMMU support? Not even VFIO does everything we need, you = may have noticed that I have to go to PCI config space to enable bus master= ing. I don't think that driver can do either of those things. Unless, of co= urse, you meant simply not tying the binding script to specific driver, whi= ch in effect is already in place (although it does check whether vfio-pci o= r igb_uio are loaded). Best regards, Anatoly Burakov DPDK SW Engineer