From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm0-f43.google.com (mail-wm0-f43.google.com [74.125.82.43]) by dpdk.org (Postfix) with ESMTP id C5F72ADB6 for ; Wed, 18 May 2016 14:39:27 +0200 (CEST) Received: by mail-wm0-f43.google.com with SMTP id a17so77406486wme.0 for ; Wed, 18 May 2016 05:39:27 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:in-reply-to :references:mime-version:content-transfer-encoding; bh=ere/wNn4uWGDEAKKH+POepm48JX35+MzjAKva6ozdmI=; b=DJaXiDM2HKFzE0SwcL1CmRnBHHJXJpgJtj97muqZI6RBFQHzdmzqkB4ufTNScV5+O9 gfGuiotk97n50qSgA4Hxy7FSvqav4ur0RfpvXCxqI8jseHhLSY4piMagLSDcHdoXn84O /KPHTtbsuySIOQ7JxX3VyRhd5PuwFFUk6puzhlKTnLhA88OIb+SIuzf/Dpz8/AtsMA3J g2N6qXnzhBQWGbscLqXLVdcnA9mraSG/6S2duR4uWasRyGw3LsQz7S/rUiS7efEiln41 kolMVCqkLDtDxTrY7ubC/raqNZeoihZ5B+TcaGcPX+8Z/DzQlrpxI1b0nPy4sfDX9gpJ VT0w== 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:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=ere/wNn4uWGDEAKKH+POepm48JX35+MzjAKva6ozdmI=; b=Odwc8xmpV+FhSiScGupEdCDcMK5nXmDpRx8Pagx78GrITApFNssUvnjyRm2n20TLjr paR3KRbC+lkAqoXYWWAQR8lkG9XMK+GGJXUEzUZ2h2FMgyOTzTmXqN14sslm9PIeA/Nm thmTwtSQbXHydMHHCgF9ROtEj8ngxkmD24owr4Qk/AG6pz0OyaFWkeIFg9vmXmEFxuxh wxYoqtJCrCVjOiwDxrWyPG7OcPfaERAPrSi6XXXL+x8OIDnwXEDdyWw4u6E71/iPRR+n T1qRYITfGqUypOfopyK5gFl16H2QmEi3F8rvlFwkaJH0sq0hJiQAvX9DLyT3I5NL1D6P uTrw== X-Gm-Message-State: AOPr4FWoDZwT7J5klr3Ge7fkMa+3Wn99wmX30BQq7beD9s/yPeD+45bZ0HoFmSiHcFhuAJEi X-Received: by 10.28.32.147 with SMTP id g141mr30319856wmg.22.1463575167451; Wed, 18 May 2016 05:39:27 -0700 (PDT) Received: from xps13.localnet (guy78-3-82-239-227-177.fbx.proxad.net. [82.239.227.177]) by smtp.gmail.com with ESMTPSA id f135sm8962825wmf.22.2016.05.18.05.39.26 (version=TLSv1/SSLv3 cipher=OTHER); Wed, 18 May 2016 05:39:26 -0700 (PDT) From: Thomas Monjalon To: Panu Matilainen Cc: Neil Horman , dev@dpdk.org, Bruce Richardson , Stephen Hemminger Date: Wed, 18 May 2016 14:38:57 +0200 Message-ID: <20348777.VsQliCQX8c@xps13> User-Agent: KMail/4.14.10 (Linux/4.1.6-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: <3ee4159d-fd29-1a20-1417-4c0a40c18779@redhat.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> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 18 May 2016 12:39:27 -0000 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 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. > - user wants to know which package(s) need to be installed to support > the system hardware You mean "which DPDK packages"? 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? > - user wants to list all supported hardware before going shopping Why doing shopping? For a DPDK usage or for a specific application? 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.