From mboxrd@z Thu Jan 1 00:00:00 1970 From: Olivier Matz Subject: Re: [dpdk-dev, RFC] drivers: advertise kmod dependencies in pmdinfo Date: Fri, 2 Sep 2016 18:13:03 +0200 Message-ID: References: <48f9320b-9402-0ecd-8971-c3785778081a@6wind.com> <20160831132709.GA32000@hmsreliant.think-freely.org> <54a0164e-b242-b930-ec91-60f91b700119@6wind.com> <348A99DA5F5B7549AA880327E580B4358909A43A@IRSMSX101.ger.corp.intel.com> <20160901173519.GA11132@hmsreliant.think-freely.org> <20160901104122.41c131be@xeon-e3> <20160901191538.GB11132@hmsreliant.think-freely.org> <348A99DA5F5B7549AA880327E580B4358909CE45@IRSMSX101.ger.corp.intel.com> <20160902133327.GA980@hmsreliant.think-freely.org> <348A99DA5F5B7549AA880327E580B4358909D016@IRSMSX101.ger.corp.intel.com> <20160902141551.GB980@hmsreliant.think-freely.org> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Cc: Stephen Hemminger , "dev@dpdk.org" , Thomas Monjalon To: Neil Horman , "Trahe, Fiona" Return-path: Received: from mail.droids-corp.org (zoll.droids-corp.org [94.23.50.67]) by dpdk.org (Postfix) with ESMTP id 8F4ED2BB3 for ; Fri, 2 Sep 2016 18:13:12 +0200 (CEST) In-Reply-To: <20160902141551.GB980@hmsreliant.think-freely.org> 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" Hi, Thank you everyone for all these comments. I'll try to summarize them here: a- the kmod information should be per-device instead of per-driver (modalias-like) b- there is no need to specify kmod dependencies (i.e. "uio_pci_generic" is enough, not "uio & uio_pci_generic") since it is available via modinfo c- the syntax with commas and colons is not ideal, we have no better consensus for now, but maybe "&" and "|" are better. d- the information provided is not complete: - some drivers requires module parameters or writing is /sys - choosing between one kmod or another is a system choice -> this info could be optional for this reason e- for usual drivers having a "" tag instead of a kmod list may be more simple (I'm not sure of it though) So we could either: - drop this RFC, and like today everyone shoule handle the loading of kmods on its own - keep the approach of this RFC, enhance it with a- b- c- e- Examples of string to manage specify the devices wildcards: /* kmod list for all pci devices */ "pci:v*:d*:sv*:sd*:vfio|uio_pci_generic|igb_uio" /* if we need device-specific modules: */ "pci:v8086:d1234:sv*:sd*:some_kmod" "pci:v8086:d4321:sv*:sd*:some_other_kmod" this is not a perfect solution, but I think it would make the development of an kmod autoload script easier. Any other idea? Thanks, Olivier