From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-we0-f173.google.com (mail-we0-f173.google.com [74.125.82.173]) by dpdk.org (Postfix) with ESMTP id 0601F678B for ; Mon, 16 Sep 2013 23:57:53 +0200 (CEST) Received: by mail-we0-f173.google.com with SMTP id w62so4240717wes.4 for ; Mon, 16 Sep 2013 14:58:32 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding:content-type; bh=Yb0FXaCX2ilpfflhwPGe+e2eqB9berXkLfxQHsdHaco=; b=jnagX2yhepcead27G560Eg+lVUU1fl5lPbuzwe9gV5dxFsYyhS8YQEGwdQr+6NhVjF P4LvWM9ApRnvsqAltTdD/7EAFZNucZkAlq8mxKFsMw33REQ7FByl26tFXtfaWo/eDr/H om2HpXN5ysjek0B2N3qSFravS1DxXeMUDqOiQfrDEgrEhjR3cVUqogGq3abph4Vj/8nt mLyO/w6gZYBnSEsE3oSaK7CEDwpmijaSqeDBHY46pae6Pxdlzvvhw6MV1VKe3RYkyQbM R8r7CvDeRbglAMC6Rxhbhhcv3STGr4SwTBiVV77Oh9yiL0hIVA11JkZD4LZ91ocS6eZy SlGQ== X-Gm-Message-State: ALoCoQnt9uCtOI4PQmNmngPl5XoPHNAWmVJ3KDadBmSHXGjKV7t101GkxEtXF8yrCN7uZHs+NOQ4 X-Received: by 10.180.160.240 with SMTP id xn16mr15147971wib.62.1379368712020; Mon, 16 Sep 2013 14:58:32 -0700 (PDT) Received: from x220.localnet (abo-26-39-68.mts.modulonet.fr. [85.68.39.26]) by mx.google.com with ESMTPSA id fz8sm143745wic.0.1969.12.31.16.00.00 (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128); Mon, 16 Sep 2013 14:58:31 -0700 (PDT) From: Thomas Monjalon To: Patrick Mahan Date: Mon, 16 Sep 2013 23:59:19 +0200 Message-ID: <1570236.KP93u3nrzz@x220> Organization: 6WIND User-Agent: KMail/4.11.1 (Linux/3.10.10-1-ARCH; KDE/4.11.1; x86_64; ; ) In-Reply-To: References: <1379363340-20870-1-git-send-email-thomas.monjalon@6wind.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH] pci: fix non-Intel devices probing 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: Mon, 16 Sep 2013 21:57:54 -0000 16/09/2013 14:42, Patrick Mahan : > On Sep 16, 2013, at 1:29 PM, Thomas Monjalon wrote: > > There is no need to check for bars mapping, especially BAR0 is not > > required. If bars mapping failed, then pci_uio_map_resource will fail and > > we won't reach this check. So get rid of BAR0 check. > > Besides, pci_uio_map_resource should only be called for Intel devices. > > The flag RTE_PCI_DRV_NEED_IGB_UIO is set for all Intel devices, even when > > RTE_EAL_UNBIND_PORTS is disabled. > > I totally disagree with this statement. I am currently working on a > non-intel device that does need UIO support (I copied the igb UIO to create > a new UIO driver). This device not only needs bar0 but also bar1. I've > modified the eal PCI support code to support this behavior and change this > behavior would not be good, IMHO. I don't know which statement you are talking about. You are writing a PMD based on UIO. Will you send it on dpdk.org ? In this release, the only PMDs using UIO are Intel ones. Also as explained, this check is never needed. But I think you are talking about support of BAR mapping. This is not changed by this patch. Moreover, the BAR mapping is extended in coming release 1.4.1. Note that it's simpler to discuss about a patch or a clearly pointed sentence. So, please be more precise or send your patch proposal. PS: please don't top-post -- Thomas