From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-oa0-f44.google.com (mail-oa0-f44.google.com [209.85.219.44]) by dpdk.org (Postfix) with ESMTP id DD348B372 for ; Thu, 28 Aug 2014 14:37:54 +0200 (CEST) Received: by mail-oa0-f44.google.com with SMTP id o6so530373oag.3 for ; Thu, 28 Aug 2014 05:42:03 -0700 (PDT) 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:content-type; bh=9CNNl3l93qjs8+wZeAf76piDucL73Lh8OJ8rVgWKJfE=; b=dSc3KcwrIyqh0oZqL1jePg8php4wJdSkBn4flmv84bTWTuUETIYgWnv+kNYopjuxKz mfL0mn9HoL2fJNPcoZEnC3detRXjpB0zmZvBSMGpegKdGgrYvJcSCofVBjyd0PR14IAo S0KnquJWBtkaRkgWdP3G2kilL7GRLXy5XLuPYi9GTqdMnogFr42dODAaW0GwqpjvQoEZ GMC2nt4wjZ0Bwg1kYiiGYhMuXILrLvwXCfv0Z+Be27k2Aq/VmVwyy63SH+4iatsOM6vX QyNvPSc89BJa2T8xn1QYzB7LoS1hqtnCt08vlvqILNzsn6UHADiuqCiIFIT9NQMWyhHM at3A== X-Gm-Message-State: ALoCoQnOFD1s/LMQhfMUAMU7lgGlm9T/GI85i1m7gh7alKLlA1MmENlay1IfAmW43fH+r6/4Q2wR MIME-Version: 1.0 X-Received: by 10.60.133.103 with SMTP id pb7mr3390405oeb.48.1409229722965; Thu, 28 Aug 2014 05:42:02 -0700 (PDT) Received: by 10.202.214.88 with HTTP; Thu, 28 Aug 2014 05:42:02 -0700 (PDT) In-Reply-To: References: Date: Thu, 28 Aug 2014 14:42:02 +0200 Message-ID: From: David Marchand To: =?UTF-8?B?7J206re87ZmN?= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [ethdev] Multiple devices with single PCI 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, 28 Aug 2014 12:37:55 -0000 Hello, On Thu, Aug 28, 2014 at 12:54 PM, =EC=9D=B4=EA=B7=BC=ED=99=8D wrote: > I found that DPDK has an abstraction for having multiple devices with > single PCI. > (RTE_PCI_DRV_MULTIPLE flag) > However, their is a naming collision while registering multiple devices. > Here is my possible solution. > - Actually, I think this flag could just disappear. It had been added at a time when ethdev objects could only be created through eth_drivers. Right now, a pci driver can create ethdev objects using rte_eth_dev_allocate(thenameyouwant). So I would rather propose you convert your driver from a eth_driver to a pci_driver. It is not that hard, you only need to allocate your own private structure and ensure the mandatory fields are filled. You can look at rte_eth_dev_init() to see what is needed. - Thomas, RTE_PCI_DRV_MULTIPLE deprecation for 1.8.x ? --=20 David Marchand