From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-yw0-f176.google.com (mail-yw0-f176.google.com [209.85.161.176]) by dpdk.org (Postfix) with ESMTP id 718F85A72 for ; Thu, 12 May 2016 05:42:27 +0200 (CEST) Received: by mail-yw0-f176.google.com with SMTP id j74so62032716ywg.1 for ; Wed, 11 May 2016 20:42:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc; bh=GlCSaApvcGRPP3ipEDGHkKZ85MF+l7oWH9N3PW0bTIU=; b=H5Mzim57W77UlPTPREufXdImhZJadEbroozQVaTEJB1GGgKn3R4JLVo4COeSpd2LKh 0gaiiRlq5gH3PYz827QdNc/VveizvCTSf7N0mSlu5ZNQUEtyoFYvFtQBMRSNJbmJsJIY Feh74L7Z2eXcTm0wKptPACopOE957YWTqWwBc= 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; bh=GlCSaApvcGRPP3ipEDGHkKZ85MF+l7oWH9N3PW0bTIU=; b=Qj/461DoC/AOTw5hnsbet0FuvT7hbl26kfFf/cnbSi5Z9FS7GfVm8nWo09UXPgofLi 1YB3Cgc4z5oKG5SjoA2X8C2XZ3r1oppCI60XzsHG9czfTt3dYXZLgv1stySjESFMYy/B UPwN/k/KU1+E3OebIs7XGb8PE71/D0pE7cwvP9YaU1TU6bntZHyVJU78WnqQ7qDE7HQg VsDLvUTgU+7wYrRdCaDubVw5i1oLkKa990lMtpeo67hi17O0E6PnrHokE3nFECqRDqi9 sjkoP/j3t66R8McqYoXV4dl+3DsIdrEjr8Fa+MxtIULKFuKk3PKqFxybeNjotwXCYnsv n04w== X-Gm-Message-State: AOPr4FUcyKcx/0FV0H1cxHTrCFAjM7a8CMn2vnV1lVlYDyWNYyujnaWKlQHmq5qaImzNMTMButub2kzmRLUielSM MIME-Version: 1.0 X-Received: by 10.37.91.69 with SMTP id p66mr3250083ybb.127.1463024546908; Wed, 11 May 2016 20:42:26 -0700 (PDT) Received: by 10.37.223.2 with HTTP; Wed, 11 May 2016 20:42:26 -0700 (PDT) In-Reply-To: <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> <20160512031642.GA5855@santosh-Latitude-E5530-non-vPro> Date: Thu, 12 May 2016 11:42:26 +0800 Message-ID: From: Jianbo Liu To: Santosh Shukla Cc: Stephen Hemminger , Jerin Jacob , Hemant Agrawal , dev@dpdk.org, Thomas Monjalon Content-Type: text/plain; charset=UTF-8 Subject: Re: [dpdk-dev] [PATCHv3 1/2] config/armv8a: disable 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, 12 May 2016 03:42:27 -0000 On 12 May 2016 at 11:17, Santosh Shukla wrote: > On Thu, May 12, 2016 at 10:01:05AM +0800, Jianbo Liu wrote: >> On 12 May 2016 at 02:25, Stephen Hemminger wrote: >> > On Wed, 11 May 2016 22:32:16 +0530 >> > Jerin Jacob 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 wrote: >> >> > >> >> > > IGB_UIO not supported for arm64 arch in kernel so disable. >> >> > > >> >> > > Signed-off-by: Hemant Agrawal >> >> > > Reviewed-by: Santosh Shukla >> >> > >> >> > 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 Most likely they don't have local dpdk tree. They write their own applications, complie and link to dpdk lib, then done. > dpdk tree. Why are you imposing user-x custome depedancy on upstream dpdk base Customer requiremnts is important. I want they can choose the way they like. > 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 You are wrong, he can build dpdk. If he like to use upstream without patching, he can use vfio. But you can't ignore the need from old user which is more comfortable with older kernel. > sense. >