From: "Rosen, Rami" <rami.rosen@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>,
"george.dit@gmail.com" <george.dit@gmail.com>
Cc: "users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] Retrieve NIC vendor name using PCI vendor ID
Date: Sun, 10 Sep 2017 18:55:28 +0000 [thread overview]
Message-ID: <9B0331B6EBBD0E4684FBFAEDA55776F93DEA374B@HASMSX110.ger.corp.intel.com> (raw)
In-Reply-To: <20170908085538.1161cf68@xeon-e3>
Hi, George,
>There already is a standard library for this (libpci).
>I see no reason to add this to DPDK.
+1.
Follow in pciutils execution of, for example,
"lspci -d 8086:158b"
Where you get, for example:
03:00.0 Ethernet controller: Intel Corporation Device 158b (rev 02)
(or any other vendrID:DeviceID combo).
I would guess that behinds the scenes it is done by pci_lookup_name():
https://github.com/pciutils/pciutils/blob/master/lib/names.c#L122
Regards,
Rami Rosen
next prev parent reply other threads:[~2017-09-10 18:55 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-08 13:35 george.dit
2017-09-08 15:55 ` Stephen Hemminger
2017-09-10 18:55 ` Rosen, Rami [this message]
2017-09-11 7:10 ` george.dit
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=9B0331B6EBBD0E4684FBFAEDA55776F93DEA374B@HASMSX110.ger.corp.intel.com \
--to=rami.rosen@intel.com \
--cc=george.dit@gmail.com \
--cc=stephen@networkplumber.org \
--cc=users@dpdk.org \
/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).