From: Krishnamurthy Srinivasan <kssrinivasan@google.com>
To: David Marchand <david.marchand@redhat.com>
Cc: users@dpdk.org, Maciej Skrocki <maciejskrocki@google.com>,
Beilei Xing <beilei.xing@intel.com>,
Jeff Guo <jia.guo@intel.com>,
Jingjing Wu <jingjing.wu@intel.com>,
"Connolly, Padraig J" <padraig.j.connolly@intel.com>
Subject: Re: [dpdk-users] Help with error: *** Did not find any ports to use ***
Date: Tue, 15 Dec 2020 08:36:53 -0700 [thread overview]
Message-ID: <CAMj+Vahu+Eri+p+vxQJ+QVDhDtsdk5Ke7Z5TnGJ2Q_PTtk7C3w@mail.gmail.com> (raw)
In-Reply-To: <CAMj+VahWCr9xoA8F2mpe-ga7Dvf2FbbxG1zjhGE53ADjw=ThOQ@mail.gmail.com>
I would appreciate some guidance from the i40e and iavf maintainers on
if/how we could make DPDK work with this NIC.
Thanks,
Srini
On Mon, Dec 14, 2020 at 3:07 PM Krishnamurthy Srinivasan <
kssrinivasan@google.com> wrote:
> Thanks for your prompt feedback, David.
>
> All: I would appreciate your guidance on if/how DPDK could be enabled on
> this platform.
>
> Thanks,
>
> Srini
>
> On Mon, Dec 14, 2020 at 1:52 PM David Marchand <david.marchand@redhat.com>
> wrote:
>
>> On Mon, Dec 14, 2020 at 8:46 PM Krishnamurthy Srinivasan
>> <kssrinivasan@google.com> wrote:
>> >
>> > I have seen that this error has been brought up before. However, the
>> > solutions discussed did not help resolve the error. I would appreciate
>> any
>> > help.
>> >
>> > I am running DPDK version 20.11 with Pktgen 3.7.2 on Ubuntu 20.04/K8s.
>> My
>> > server has Intel Ethernet Controller X710 for 10GbE.
>> >
>> > Here, I have configured the pod with one interface with igb-uio driver.
>> > The behavior is the same if I try pci-vfio DPDK driver. My kubectl
>> > description shows the network config to be OK:
>> >
>>
>> [snip]
>>
>> >
>> > root@master-01:~# /opt/dpdk-stable-19.11.3/usertools/dpdk-devbind.py
>> -s |
>> > more
>> >
>> > Network devices using DPDK-compatible driver
>> > ============================================
>> > 0000:41:0a.0 'Ethernet Virtual Function 700 Series 154c' drv=vfio-pci
>> > unused=iavf,igb_uio
>> > 0000:41:0a.1 'Ethernet Virtual Function 700 Series 154c' drv=vfio-pci
>> > unused=iavf,igb_uio
>> > <additional igb-uio devices>
>> > 0000:41:0a.5 'Ethernet Virtual Function 700 Series 154c' drv=igb_uio
>> > unused=iavf,vfio-pci
>> > <additional vfio-pci devices>
>>
>> Afaics, device 0x8086 / 0x154c is known by the common IAVF code base,
>> but it is associated with no PCI driver in DPDK.
>> $ git grep -w IAVF_DEV_ID_VF v20.11 --
>> v20.11:drivers/common/iavf/iavf_common.c: case
>> IAVF_DEV_ID_VF:
>> v20.11:drivers/common/iavf/iavf_devids.h:#define IAVF_DEV_ID_VF
>> 0x154C
>>
>> Copying i40e and iavf maintainers, for further guidance.
>>
>>
>> --
>> David Marchand
>>
>>
prev parent reply other threads:[~2020-12-15 15:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 5:03 Krishnamurthy Srinivasan
2020-12-14 19:46 ` Krishnamurthy Srinivasan
2020-12-14 20:52 ` David Marchand
2020-12-14 22:07 ` Krishnamurthy Srinivasan
2020-12-15 15:36 ` Krishnamurthy Srinivasan [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=CAMj+Vahu+Eri+p+vxQJ+QVDhDtsdk5Ke7Z5TnGJ2Q_PTtk7C3w@mail.gmail.com \
--to=kssrinivasan@google.com \
--cc=beilei.xing@intel.com \
--cc=david.marchand@redhat.com \
--cc=jia.guo@intel.com \
--cc=jingjing.wu@intel.com \
--cc=maciejskrocki@google.com \
--cc=padraig.j.connolly@intel.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).