From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Marchand Subject: Re: [PATCH 00/11] kill global pci device id list Date: Sat, 16 Jan 2016 16:02:45 +0100 Message-ID: References: <1452430254-30390-1-git-send-email-david.marchand@6wind.com> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: "dev@dpdk.org" To: "Zhang, Helin" Return-path: Received: from mail-oi0-f50.google.com (mail-oi0-f50.google.com [209.85.218.50]) by dpdk.org (Postfix) with ESMTP id 2F1E78E91 for ; Sat, 16 Jan 2016 16:03:06 +0100 (CET) Received: by mail-oi0-f50.google.com with SMTP id k206so153190638oia.1 for ; Sat, 16 Jan 2016 07:03:06 -0800 (PST) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" Hello Helin, On Sun, Jan 10, 2016 at 4:53 PM, Zhang, Helin wrote: > Thanks for your huge contribution! > May you help to describe more details of why you made these huge changes? As far as I can see, the only reason why we have a centralised header maintained in eal with all pci device ids is the need to identify pci devices that require a special treatment before starting a dpdk application (here, bind those pci devices to igb_uio / vfio). This patchset splits this header into small pieces maintained by the drivers themselves, then tries to come up with a way to retrieve those pci device ids from the final dpdk application and from the drivers compiled as shared libraries. With this, supported pci device ids are maintained by the drivers themselves rather than eal, pci devices ids requiring uio/vfio binding are still available. Regards, -- David Marchand