From: Stephen Hemminger <stephen@networkplumber.org>
To: george.dit@gmail.com
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Retrieve NIC vendor name using PCI vendor ID
Date: Fri, 8 Sep 2017 08:55:38 -0700 [thread overview]
Message-ID: <20170908085538.1161cf68@xeon-e3> (raw)
In-Reply-To: <CAN9HtFCVoNzzgFLbuu+RYuUCc3WoOcf=Ph1P1OP+hwmRM9hDEA@mail.gmail.com>
On Fri, 8 Sep 2017 06:35:59 -0700
george.dit@gmail.com wrote:
> Hi all,
>
> I would like to ask how one could retrieve the name of a NIC's vendor using
> the PCI vendor ID.
> For example, is there any mapping between PCI_VENDOR_ID_INTEL and a const
> char* that returns e.g., "Intel"?
>
> Moreover, why are the vendor IDs redefined by DPDK instead of being reused
> from Linux
> <https://github.com/torvalds/linux/blob/master/include/linux/pci_ids.h>?
> It would be more convenient if a single RTE library could expose those IDs
> to the applications. Currently I see those IDs being spread across the
> different drivers.
>
> Thanks in advance,
There already is a standard library for this (libpci).
I see no reason to add this to DPDK.
next prev parent reply other threads:[~2017-09-08 15: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 [this message]
2017-09-10 18:55 ` Rosen, Rami
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=20170908085538.1161cf68@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=george.dit@gmail.com \
--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).