From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Sahil Khandelwal <sahilkhandelwal05@gmail.com>, dev@dpdk.org
Subject: Re: [dpdk-dev] supported nic
Date: Tue, 14 Apr 2020 11:28:55 +0100 [thread overview]
Message-ID: <f9fa3e95-49f1-d8f7-412b-6e0dd94fce52@intel.com> (raw)
In-Reply-To: <CACKbjtYKHkSAHHJc=NM6fbi15E2xEm4jWb6ukJ8050GPHGtveQ@mail.gmail.com>
On 4/12/2020 3:07 PM, Sahil Khandelwal wrote:
> I have the following nic in my system
> How do i check which one can be used with dpdk
>
> Network devices using kernel driver
> ===================================
> 0000:03:00.0 'RTL810xE PCI Express Fast Ethernet controller 8136' if=eno1
> drv=r8169 unused=vfio-pci,uio_pci_generic
> 0000:05:00.0 'Dual Band Wireless-AC 3168NGW [Stone Peak] 24fb' if=wlo1
> drv=iwlwifi unused=vfio-pci,uio_pci_generic *Active*
>
Network driver are under drivers/net/*, you can check if the driver for that
device exists,
and if there is any driver you suspect it may support, you can check the driver
details and which devices it support via './usertools/dpdk-pmdinfo.py' script.
For example:
./usertools/dpdk-pmdinfo.py build/lib/librte_pmd_hinic.so
PMD NAME: net_hinic
PMD HW SUPPORT:
Huawei Technologies Co., Ltd. (19e5) : Hi1822 Family (4*25GE) (1822) (All
Subdevices)
Huawei Technologies Co., Ltd. (19e5) : Unknown Device (210) (All Subdevices)
Huawei Technologies Co., Ltd. (19e5) : Unknown Device (205) (All Subdevices)
Huawei Technologies Co., Ltd. (19e5) : Hi1822 Family Virtual Function (375e)
(All Subdevices)
Huawei Technologies Co., Ltd. (19e5) : Hi1822 Family Virtual Function (379e)
(All Subdevices)
Huawei Technologies Co., Ltd. (19e5) : Unknown Device (206) (All Subdevices)
Huawei Technologies Co., Ltd. (19e5) : Unknown Device (200) (All Subdevices)
prev parent reply other threads:[~2020-04-14 10:29 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-12 14:07 Sahil Khandelwal
2020-04-14 10:28 ` Ferruh Yigit [this message]
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=f9fa3e95-49f1-d8f7-412b-6e0dd94fce52@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=sahilkhandelwal05@gmail.com \
/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).