From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <stephen@networkplumber.org>
Received: from mail-pd0-f176.google.com (mail-pd0-f176.google.com
 [209.85.192.176]) by dpdk.org (Postfix) with ESMTP id 94CBDC48E
 for <dev@dpdk.org>; Tue, 28 Apr 2015 00:06:20 +0200 (CEST)
Received: by pdbnk13 with SMTP id nk13so142372888pdb.0
 for <dev@dpdk.org>; Mon, 27 Apr 2015 15:06:19 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
 d=1e100.net; s=20130820;
 h=x-gm-message-state:date:from:to:subject:message-id:mime-version
 :content-type:content-transfer-encoding;
 bh=51M7Jpe8IH0cmuxtfCAKlR5z6TC31A5pEfPWDazS/hQ=;
 b=Z86kh+ihPfHQrbb/FX+x7psUjJRnACOTrL2eeOT5WM/V0L8EbnpF/4YG9qIZ5SJlfX
 4fTlYnbLlR5LuvDO/tK/iNm87zi/jjxjw927CYtgYATBPn9b30chV7HxBZDDKSNbvcus
 v+xFkKqNyoUZz9QtDIW1lHEo+DFjUm6B8RtJ+UIyUiktKOuJN60e+wiybnJfjLEhDit0
 lMC0xouUIVzFqJncX9Mt6yqDQLq6SJpIYsniei8RJhcv9Q36uwKEYeEJCGAbKjNAVB1F
 WVq+TYR/mpWdQeoQWBzZGv5RZav78dLsL5GNesCch+pUwgAfvM9b4v+vFPtWfgCzItM1
 tOAQ==
X-Gm-Message-State: ALoCoQkn+1hfSlqFwkuXLMWIgI41rN6/V2Zj+bFpDuvlXtShBV+PjHcsPL8QJ3PaBHJxshXeQYzt
X-Received: by 10.66.120.196 with SMTP id le4mr26236882pab.53.1430172379727;
 Mon, 27 Apr 2015 15:06:19 -0700 (PDT)
Received: from urahara (static-50-53-82-155.bvtn.or.frontiernet.net.
 [50.53.82.155])
 by mx.google.com with ESMTPSA id fu14sm20532225pad.44.2015.04.27.15.06.19
 for <dev@dpdk.org>
 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);
 Mon, 27 Apr 2015 15:06:19 -0700 (PDT)
Date: Mon, 27 Apr 2015 15:06:24 -0700
From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Message-ID: <20150427150624.68ef88bc@urahara>
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Subject: [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: Mon, 27 Apr 2015 22:06:21 -0000

I raised the issue, but people seem to be ignoring that fact that igb_uio
was broken by the introduction of UIO PCI generic in 2.0.

There are three options:
 1. Remove IGB_UIO only use UIO PCI generic.
    Downside there is no MSI-X support for UIO PCI generic.
 2. Revert UIO PCI generic support
 3. Replace both of the above with something better.

I am working on #3 but it will not be ready for 2.0.1 and there
is no solution for users of 2.0 and any future stable code.