From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-pa0-f45.google.com (mail-pa0-f45.google.com [209.85.220.45]) by dpdk.org (Postfix) with ESMTP id 426F98E61 for ; Fri, 2 Oct 2015 02:04:43 +0200 (CEST) Received: by pacex6 with SMTP id ex6so89178108pac.0 for ; Thu, 01 Oct 2015 17:04:41 -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:cc:subject:message-id:in-reply-to :references:mime-version:content-type:content-transfer-encoding; bh=GqksUcdLKB8Wea/Kqm84tBCRfEdiyydlIDtPf9Osyn0=; b=WxNvBtiJVT9wN57TO48jCJIE6B/yfT35BCAwwmWckcv54d5jVSOFYIui1ZBhNom+i+ VDxdYqsgywYYa6/LGLg7S9faYpvpS2RdiXLmGaTjSsyDshOpyNzGvzRejutShdvlouhL KyZ94KFrGHcBSwstOWoHPEY/J0Y0i6HjTPZ8QgKb6KTWPjt/ExQqLRPeUjoRHic5TpO3 9eGC8D3Rc93H4MSlcrQBrFMQi1Gk7POmgYst/xLgcA1WuetUbz29vNTS2SvXADiNWPxD LIw30VTyeAlInggJHcCGSzqGVeEXv4gU3rOtogYKvUKDfDh8PgTJDJsX8Juy9tADRuaT ze6Q== X-Gm-Message-State: ALoCoQmgI3H1PGUfaKLt3JpcfTIj2L0lOVG78SEGczWzsOs5ywShfsNYsAl+yly0OR4Jtz3PNhwZ X-Received: by 10.67.4.9 with SMTP id ca9mr15938837pad.90.1443744281886; Thu, 01 Oct 2015 17:04:41 -0700 (PDT) Received: from urahara (static-50-53-82-155.bvtn.or.frontiernet.net. [50.53.82.155]) by smtp.gmail.com with ESMTPSA id rw8sm8949926pac.11.2015.10.01.17.04.41 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Thu, 01 Oct 2015 17:04:41 -0700 (PDT) Date: Thu, 1 Oct 2015 17:04:52 -0700 From: Stephen Hemminger To: Alexander Duyck Message-ID: <20151001170452.0e6a90c2@urahara> In-Reply-To: <560DC45A.3050507@gmail.com> References: <1443652138-31782-1-git-send-email-stephen@networkplumber.org> <1443652138-31782-3-git-send-email-stephen@networkplumber.org> <560DC45A.3050507@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org, hjk@hansjkoch.de, gregkh@linux-foundation.org, linux-kernel@vger.kernel.org Subject: Re: [dpdk-dev] [PATCH 2/2] uio: new driver to support PCI MSI-X 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: Fri, 02 Oct 2015 00:04:43 -0000 On Thu, 1 Oct 2015 16:40:10 -0700 Alexander Duyck wrote: > Do you really need to map IORESOURCE bars? Most drivers I can think of > don't use IO BARs anymore. Maybe we could look at just dropping the > code and adding it back later if we have a use case that absolutely > needs it. Mapping is not strictly necessary, but for virtio it acts a way to communicate the regions. > Also how many devices actually need resources beyond BAR 0? I'm just > curious as I know BAR 2 on many of the Intel devices is the register > space related to MSI-X so now we have both the PCIe subsystem and user > space with access to this region. VMXNet3 needs 2 bars. Most use only one.