From: Ferruh Yigit <ferruh.yigit@xilinx.com>
To: Robin Jarry <robin@jarry.cc>
Cc: Olivier Matz <olivier.matz@6wind.com>, <dev@dpdk.org>
Subject: Re: [PATCH] usertools: rewrite pmdinfo
Date: Tue, 13 Sep 2022 12:29:33 +0100 [thread overview]
Message-ID: <467bb09c-34ec-811f-9781-bc7ad5d63e42@xilinx.com> (raw)
In-Reply-To: <20220913105811.84384-1-robin@jarry.cc>
On 9/13/2022 11:58 AM, Robin Jarry wrote:
> dpdk-pmdinfo.py does not produce any parseable output. The -r/--raw flag
> merely prints multiple independent JSON lines which cannot be fed
> directly to any JSON parser. Moreover, the script complexity is rather
> high for such a simple task: extracting PMD_INFO_STRING from .rodata ELF
> sections. Rewrite it so that it can produce valid JSON.
>
> Remove the PCI database parsing for PCI-ID to Vendor-Device names
> conversion. This should be done by external scripts (if really needed).
>
> Here are some examples of use with jq:
>
> Get the complete info for a given driver:
>
> ~$ usertools/dpdk-pmdinfo.py build/app/dpdk-testpmd | \
> jq '.[] | select(.name == "dmadev_idxd_pci")'
> {
> "name": "dmadev_idxd_pci",
> "params": "max_queues=0",
> "kmod": "vfio-pci",
> "devices": [
> {
> "vendor_id": "8086",
> "device_id": "0b25",
> "subsystem_device_id": "ffff",
> "subsystem_system_id": "ffff"
> }
> ]
> }
>
> Get only the required kernel modules for a given driver:
>
> ~$ usertools/dpdk-pmdinfo.py build/app/dpdk-testpmd | \
> jq '.[] | select(.name == "net_i40e").kmod'
> "* igb_uio | uio_pci_generic | vfio-pci"
>
> Get only the required kernel modules for a given device:
>
> ~$ usertools/dpdk-pmdinfo.py build/app/dpdk-testpmd | \
> jq '.[] | select(.devices[] | .vendor_id == "15b3" and .device_id == "1013").kmod'
> "* ib_uverbs & mlx5_core & mlx5_ib"
>
> Print the list of drivers which define multiple parameters without
> string separators:
>
> ~$ usertools/dpdk-pmdinfo.py build/app/dpdk-testpmd | \
> jq '.[] | select(.params!=null and (.params|test("=[^ ]+="))) | {name, params}'
> ...
>
> The script passes flake8, black, isort and pylint checks.
>
> I have tested this with a matrix of python/pyelftools versions:
>
> pyelftools
> 0.22 0.23 0.24 0.25 0.26 0.27 0.28 0.29
> 3.6 ok ok ok ok ok ok ok ok
> 3.7 ok ok ok ok ok ok ok ok
> Python 3.8 ok ok ok ok ok ok ok ok
> 3.9 ok ok ok ok ok ok ok ok
> 3.10 fail fail fail fail ok ok ok ok
>
> All failures with python 3.10 are related to the same issue:
>
> File "elftools/construct/lib/container.py", line 5, in <module>
> from collections import MutableMapping
> ImportError: cannot import name 'MutableMapping' from 'collections'
>
> Python 3.10 support is only available since pyelftools 0.26.
>
> NB: The output produced by the legacy -r/--raw flag can be obtained with
> the following command:
>
> strings build/app/dpdk-testpmd | sed -n 's/^PMD_INFO_STRING= //p'
>
> Cc: Olivier Matz<olivier.matz@6wind.com>
> Signed-off-by: Robin Jarry<robin@jarry.cc>
Hi Robin,
Thanks for the work.
One of the major usecase of the script is to get information from binary
drivers. So intentions of the script is to run it on drivers more than
applications (dpdk-testpmd).
When I run it on one of the .so drivers, it is generating some warnings
[1], is this expected?
[1]
$ ./usertools/dpdk-pmdinfo.py ./build/drivers/librte_net_ixgbe.so
warning: cannot find librte_ethdev.so.23
warning: cannot find librte_eal.so.23
warning: cannot find librte_kvargs.so.23
warning: cannot find librte_telemetry.so.23
warning: cannot find librte_net.so.23
warning: cannot find librte_mbuf.so.23
warning: cannot find librte_mempool.so.23
warning: cannot find librte_ring.so.23
warning: cannot find librte_meter.so.23
warning: cannot find librte_bus_pci.so.23
warning: cannot find librte_pci.so.23
warning: cannot find librte_bus_vdev.so.23
warning: cannot find librte_hash.so.23
warning: cannot find librte_rcu.so.23
warning: cannot find librte_security.so.23
warning: cannot find librte_cryptodev.so.23
[
{
"name": "net_ixgbe_vf",
"params": "pflink_fullchk=<0|1>",
"kmod": "* igb_uio | vfio-pci",
"devices": [
...
...
next prev parent reply other threads:[~2022-09-13 11:29 UTC|newest]
Thread overview: 42+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-13 10:58 Robin Jarry
2022-09-13 11:29 ` Ferruh Yigit [this message]
2022-09-13 11:49 ` Robin Jarry
2022-09-13 13:50 ` Ferruh Yigit
2022-09-13 13:59 ` Robin Jarry
2022-09-13 14:17 ` Ferruh Yigit
2022-09-13 14:17 ` Bruce Richardson
2022-09-13 19:42 ` [PATCH v2] " Robin Jarry
2022-09-13 20:54 ` Ferruh Yigit
2022-09-13 21:22 ` Robin Jarry
2022-09-14 11:46 ` Ferruh Yigit
2022-09-15 9:18 ` Robin Jarry
2022-09-20 9:08 ` [PATCH v3] " Robin Jarry
2022-09-20 10:10 ` Ferruh Yigit
2022-09-20 10:12 ` Robin Jarry
2022-09-20 10:42 ` [PATCH v4] " Robin Jarry
2022-09-20 14:08 ` Olivier Matz
2022-09-20 17:48 ` Ferruh Yigit
2022-09-20 17:50 ` Ferruh Yigit
2022-09-21 7:27 ` Thomas Monjalon
2022-09-21 8:02 ` Ferruh Yigit
2022-09-20 19:15 ` Robin Jarry
2022-09-21 7:58 ` Ferruh Yigit
2022-09-21 9:57 ` Ferruh Yigit
2022-09-22 11:58 ` [PATCH v5] " Robin Jarry
2022-09-22 12:03 ` Bruce Richardson
2022-09-22 15:12 ` Ferruh Yigit
2022-09-26 11:55 ` Olivier Matz
2022-09-26 12:52 ` Robin Jarry
2022-09-26 13:44 ` [PATCH v6] " Robin Jarry
2022-09-26 15:17 ` Bruce Richardson
2022-09-28 6:51 ` Robin Jarry
2022-09-28 10:53 ` Bruce Richardson
2022-09-28 11:12 ` Robin Jarry
2022-10-04 19:29 ` [PATCH v7] " Robin Jarry
2022-10-10 22:44 ` Thomas Monjalon
2022-10-12 15:16 ` Olivier Matz
2022-10-12 16:16 ` Thomas Monjalon
2022-10-12 16:30 ` Robin Jarry
2022-10-12 16:44 ` Thomas Monjalon
2022-10-12 16:48 ` Robin Jarry
2022-10-12 20:40 ` Thomas Monjalon
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=467bb09c-34ec-811f-9781-bc7ad5d63e42@xilinx.com \
--to=ferruh.yigit@xilinx.com \
--cc=dev@dpdk.org \
--cc=olivier.matz@6wind.com \
--cc=robin@jarry.cc \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).