From mboxrd@z Thu Jan  1 00:00:00 1970
From: Santosh Shukla <santosh.shukla@caviumnetworks.com>
Subject: Re: [PATCHv3 1/2] config/armv8a: disable igb_uio
Date: Thu, 12 May 2016 08:47:10 +0530
Message-ID: <20160512031642.GA5855@santosh-Latitude-E5530-non-vPro>
References: <1462974479-26180-1-git-send-email-hemant.agrawal@nxp.com>
 <20160511082259.42905f98@xeon-e3>
 <20160511170215.GA1637@localhost.localdomain>
 <20160511112559.69dcff13@xeon-e3>
 <CAP4Qi39YnbOAv8ToaNjc7PnBf=ZDhD3Ofep4SFNnvNmrDBjquQ@mail.gmail.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Cc: Stephen Hemminger <stephen@networkplumber.org>, Jerin Jacob
 <jerin.jacob@caviumnetworks.com>, Hemant Agrawal <hemant.agrawal@nxp.com>,
 <dev@dpdk.org>, Thomas Monjalon <thomas.monjalon@6wind.com>
To: Jianbo Liu <jianbo.liu@linaro.org>
Return-path: <dev-bounces@dpdk.org>
Received: from na01-bn1-obe.outbound.protection.outlook.com
 (mail-bn1bon0093.outbound.protection.outlook.com [157.56.111.93])
 by dpdk.org (Postfix) with ESMTP id DB6796910
 for <dev@dpdk.org>; Thu, 12 May 2016 05:17:36 +0200 (CEST)
Content-Disposition: inline
In-Reply-To: <CAP4Qi39YnbOAv8ToaNjc7PnBf=ZDhD3Ofep4SFNnvNmrDBjquQ@mail.gmail.com>
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>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On Thu, May 12, 2016 at 10:01:05AM +0800, Jianbo Liu wrote:
> On 12 May 2016 at 02:25, Stephen Hemminger <stephen@networkplumber.org> wrote:
> > On Wed, 11 May 2016 22:32:16 +0530
> > Jerin Jacob <jerin.jacob@caviumnetworks.com> wrote:
> >
> >> On Wed, May 11, 2016 at 08:22:59AM -0700, Stephen Hemminger wrote:
> >> > On Wed, 11 May 2016 19:17:58 +0530
> >> > Hemant Agrawal <hemant.agrawal@nxp.com> wrote:
> >> >
> >> > > IGB_UIO not supported for arm64 arch in kernel so disable.
> >> > >
> >> > > Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
> >> > > Reviewed-by: Santosh Shukla <santosh.shukla@caviumnetworks.com>
> >> >
> >> > Really, I have use IGB_UIO on ARM64
> >>
> >> May I know what is the technical use case for igb_uio on arm64
> >> which cannot be addressed through vfio or vfioionommu.
> >
> > I was running on older kernel which did not support vfioionommu mode.
> 
> As I said, most of DPDK developers are not kernel developers. They may
> have their own kernel tree, and couldn't like to upgrade to latest
> kernel.
> They can choose to use or not use igb_uio when binding the driver. But
> blindly disabling it in the base config seems unreasonable.

if user keeping his own kernel so they could also keep IGB_UIO=y in their local
dpdk tree. Why are you imposing user-x custome depedancy on upstream dpdk base
config. Is it not enough for explanation that - Base config ie.. armv8 doesn;t
support pci mmap, so igb_uio is n/a. New user wont able to build/run dpdk/arm64
in igb_uio-way, He'll prefer to use upstream stuff. I think, you are not making
sense.