From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <pmatilai@redhat.com> Received: from mx1.redhat.com (mx1.redhat.com [209.132.183.28]) by dpdk.org (Postfix) with ESMTP id B4327B442 for <dev@dpdk.org>; Wed, 18 May 2016 15:09:28 +0200 (CEST) Received: from int-mx13.intmail.prod.int.phx2.redhat.com (int-mx13.intmail.prod.int.phx2.redhat.com [10.5.11.26]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.redhat.com (Postfix) with ESMTPS id D30027F0A3; Wed, 18 May 2016 13:09:27 +0000 (UTC) Received: from sopuli.koti.laiskiainen.org (vpn1-5-221.ams2.redhat.com [10.36.5.221]) by int-mx13.intmail.prod.int.phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u4ID9Ptx026540; Wed, 18 May 2016 09:09:26 -0400 To: Thomas Monjalon <thomas.monjalon@6wind.com> References: <1463431287-4551-1-git-send-email-nhorman@tuxdriver.com> <1463431287-4551-5-git-send-email-nhorman@tuxdriver.com> <3ee4159d-fd29-1a20-1417-4c0a40c18779@redhat.com> <20348777.VsQliCQX8c@xps13> Cc: Neil Horman <nhorman@tuxdriver.com>, dev@dpdk.org, Bruce Richardson <bruce.richardson@intel.com>, Stephen Hemminger <stephen@networkplumber.org> From: Panu Matilainen <pmatilai@redhat.com> Message-ID: <9583b572-d793-7b3f-1de9-facd0925ea56@redhat.com> Date: Wed, 18 May 2016 16:09:25 +0300 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: <20348777.VsQliCQX8c@xps13> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-Scanned-By: MIMEDefang 2.68 on 10.5.11.26 X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-4.5.16 (mx1.redhat.com [10.5.110.26]); Wed, 18 May 2016 13:09:28 +0000 (UTC) Subject: Re: [dpdk-dev] [PATCH 4/4] pmd_hw_support.py: Add tool to query binaries for hw support information X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK <dev.dpdk.org> List-Unsubscribe: <http://dpdk.org/ml/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://dpdk.org/ml/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <http://dpdk.org/ml/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> X-List-Received-Date: Wed, 18 May 2016 13:09:29 -0000 On 05/18/2016 03:38 PM, Thomas Monjalon wrote: > 2016-05-18 14:48, Panu Matilainen: >> Calling up on the list of requirements from >> http://dpdk.org/ml/archives/dev/2016-May/038324.html, I see a pile of >> technical requirements but perhaps we should stop for a moment to think >> about the use-cases first? >> >> To name some from the top of my head: >> - user wants to know whether the hardware on the system is supported > > supported by what? > * by a statically linked app > * by a DPDK he has downloaded and built > * by a DPDK provided as shared library by its Linux vendor All three? > In the first 2 cases he knows where the files are. > In the Linux distribution case, there can be a default directory set > by the Linux vendor for the script looking at the infos. Only the Linux > vendor knows where the PMDs files are. For case 3), EAL and the DPDK build system know where the PMDs are via CONFIG_RTE_EAL_PMD_PATH (if set of course, otherwise there's not much hope) > >> - user wants to know which package(s) need to be installed to support >> the system hardware > > You mean "which DPDK packages"? Yes. This is of course only relevant if PMDs are split across several different packages (splitting might not make much sense yet, but as the number grows that might well change) > Are some informations showed when doing "packager search dpdk"? > or "packager show dpdk-driverX"? > Do you want to show the PCI ids in the description of the packages? Something along those lines - such things are being done by distros for eg firmware, printer drivers, kernel drivers by modalias etc. >> - user wants to list all supported hardware before going shopping > > Why doing shopping? For a DPDK usage or for a specific application? To buy hardware which is supported by DPDK, in a general case. > The application should mentions the supported hardware. > For more general DPDK information, there is this this page: > http://dpdk.org/doc/nics > But it may be not enough accurate for some PCI id exceptions. > For more details, he must use a listing tool. Yes. The point is, what kind of tool/solution can be made to behave identically between shared and static configs, in a user-friendly way. I just listed a few obvious (to me at least) use-cases, and was asking for others that I didn't think of. - Panu -