From: David Marchand <david.marchand@redhat.com>
To: "Antón Rey Villaverde" <anton.rey@cactussoft.biz>,
simei <simei.su@intel.com>, "Wenjun Wu" <wenjun1.wu@intel.com>
Cc: dev@dpdk.org, Qi Zhang <qi.z.zhang@intel.com>,
"Mcnamara, John" <john.mcnamara@intel.com>,
Qiming Yang <qiming.yang@intel.com>
Subject: Re: Troubleshooting DPDK in Intel Ethernet NIC
Date: Fri, 8 Sep 2023 11:15:01 +0200 [thread overview]
Message-ID: <CAJFAV8yjdZEYKds3ZZn+rtahVh5Z9WRAjTLs7gv+qQyVPoObuQ@mail.gmail.com> (raw)
In-Reply-To: <CAGFBTqoXPiJp=KET07KqoCpZEgqT_sQsaS1DaqQC5uHUBnTFyQ@mail.gmail.com>
On Fri, Sep 8, 2023 at 11:05 AM Antón Rey Villaverde
<anton.rey@cactussoft.biz> wrote:
> > Afaics, this nic is not supported by DPDK drivers.
>
> Indeed there is nothing about "15fb" (the PCI ID of my NIC) in the output of ./usertools/dpdk-pmdinfo.py build/app/dpdk-testpmd , so I guess it is not supported.
>
> On the other hand, I do see that the I219 family of my NIC (I219-LM) is present in the list https://core.dpdk.org/supported/nics/intel/ under e1000e category.
>
> Is this a contradiction or am I missing something?
I reached the point where I can't help :-).
Some I219 nics support has been added ealier this year (commit
a33e1a5bcd3f ("net/e1000: support more I219 devices")).
Maybe adding support for your nic is a simple matter, but passing the
ball to Intel maintainers who are the right people to answer.
--
David Marchand
prev parent reply other threads:[~2023-09-08 9:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-07 14:57 Antón Rey Villaverde
2023-09-08 7:10 ` David Marchand
2023-09-08 9:04 ` Antón Rey Villaverde
2023-09-08 9:15 ` David Marchand [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=CAJFAV8yjdZEYKds3ZZn+rtahVh5Z9WRAjTLs7gv+qQyVPoObuQ@mail.gmail.com \
--to=david.marchand@redhat.com \
--cc=anton.rey@cactussoft.biz \
--cc=dev@dpdk.org \
--cc=john.mcnamara@intel.com \
--cc=qi.z.zhang@intel.com \
--cc=qiming.yang@intel.com \
--cc=simei.su@intel.com \
--cc=wenjun1.wu@intel.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).