From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <michael.qiu@intel.com>
Received: from mga11.intel.com (mga11.intel.com [192.55.52.93])
 by dpdk.org (Postfix) with ESMTP id F358FC4D2
 for <dev@dpdk.org>; Tue, 28 Apr 2015 10:07:24 +0200 (CEST)
Received: from orsmga002.jf.intel.com ([10.7.209.21])
 by fmsmga102.fm.intel.com with ESMTP; 28 Apr 2015 01:07:24 -0700
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos;i="5.11,662,1422950400"; d="scan'208";a="720317001"
Received: from pgsmsx106.gar.corp.intel.com ([10.221.44.98])
 by orsmga002.jf.intel.com with ESMTP; 28 Apr 2015 01:07:22 -0700
Received: from shsmsx151.ccr.corp.intel.com (10.239.6.50) by
 PGSMSX106.gar.corp.intel.com (10.221.44.98) with Microsoft SMTP Server (TLS)
 id 14.3.224.2; Tue, 28 Apr 2015 16:07:19 +0800
Received: from shsmsx101.ccr.corp.intel.com ([169.254.1.107]) by
 SHSMSX151.ccr.corp.intel.com ([169.254.3.77]) with mapi id 14.03.0224.002;
 Tue, 28 Apr 2015 16:07:18 +0800
From: "Qiu, Michael" <michael.qiu@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>, "dev@dpdk.org"
 <dev@dpdk.org>
Thread-Topic: [dpdk-dev] What to do about UIO breakage in 2.0
Thread-Index: AQHQgTZw3xObEF9atUyNBs/8z9mDGA==
Date: Tue, 28 Apr 2015 08:07:18 +0000
Message-ID: <533710CFB86FA344BFBF2D6802E602860466909F@SHSMSX101.ccr.corp.intel.com>
References: <20150427150624.68ef88bc@urahara>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach: 
X-MS-TNEF-Correlator: 
x-originating-ip: [10.239.127.40]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Subject: Re: [dpdk-dev] What to do about UIO breakage in 2.0
X-BeenThere: dev@dpdk.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: patches and discussions about DPDK <dev.dpdk.org>
List-Unsubscribe: <http://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <http://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Apr 2015 08:07:25 -0000

On 4/28/2015 6:06 AM, Stephen Hemminger wrote:=0A=
> I raised the issue, but people seem to be ignoring that fact that igb_uio=
=0A=
> was broken by the introduction of UIO PCI generic in 2.0.=0A=
=0A=
What do you mean about igb_uio broken?=0A=
=0A=
Thanks,=0A=
Michael=0A=
>=0A=
> There are three options:=0A=
>  1. Remove IGB_UIO only use UIO PCI generic.=0A=
>     Downside there is no MSI-X support for UIO PCI generic.=0A=
>  2. Revert UIO PCI generic support=0A=
>  3. Replace both of the above with something better.=0A=
>=0A=
> I am working on #3 but it will not be ready for 2.0.1 and there=0A=
> is no solution for users of 2.0 and any future stable code.=0A=
>=0A=
=0A=