From: Reeve Yang <reeve.yang@gmail.com>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] rte_eth_dev_count() returns 0 with ENA device
Date: Thu, 6 Jun 2019 17:21:55 -0700 [thread overview]
Message-ID: <CAGNTBAUP15fKb5cGKMDemnK-aAWGpkpNUQj64PifiNZ=7me00w@mail.gmail.com> (raw)
In-Reply-To: <CAGNTBAULGBcUdhx9wzEEWF2d9RDm0pmisL_F=g__UuLVY=A3ug@mail.gmail.com>
some followup ... I debugged more, it looks like rte_pci_probe is not
happening, so the rte_eth_dev_allocate is not called at all ..., buy
why is that? I ran testpmd, it shows no probed ethernet device.
# /opt/bluecoat/sslv/bin/testpmd testpmd -n 2 -l 2-3 -w 0000:00:04.0
-m 256 -- -i
EAL: Detected 48 lcore(s)
EAL: Multi-process socket /var/run/.rte_unix
EAL: Probing VFIO support...
testpmd: No probed ethernet devices
Interactive-mode selected
...
Any help is greatly appreciated
On Thu, Jun 6, 2019 at 2:26 PM Reeve Yang <reeve.yang@gmail.com> wrote:
>
> Hi Gurus,
>
> I'm trying to bring VM under Amzaon EC2 R4.16xlarge instance, so the
> ethernet device is uising Amazon ENA driver. The kernel is 3.10, dpdk
> is 18.02. All ether device are bound successfully, but for some
> reason, the DPDK data path cannot be initialized because
> rte_eth_dev_count() always returns zero. Can someone shed some lights?
> Thanks.
>
> I'm pretty sure the VM instance is set up correctly in terms ENA enabled.
>
> Below are some details:
> # modinfo ena
> filename:
> /lib/modules/3.10.0-693.11.6.el7.228052.x86_64/kernel/drivers/net/ethernet/amazon/ena/ena.ko.xz
> version: 1.0.2
> license: GPL
> description: Elastic Network Adapter (ENA)
> author: Amazon.com, Inc. or its affiliates
> rhelversion: 7.4
>
> # lspci -vt
> -[0000:00]-+-00.0 Intel Corporation 440FX - 82441FX PMC [Natoma]
> +-01.0 Intel Corporation 82371SB PIIX3 ISA [Natoma/Triton II]
> +-01.1 Intel Corporation 82371SB PIIX3 IDE [Natoma/Triton II]
> +-01.3 Intel Corporation 82371AB/EB/MB PIIX4 ACPI
> +-02.0 Cirrus Logic GD 5446
> +-03.0 Device 1d0f:ec20
> +-04.0 Device 1d0f:ec20
> +-05.0 Device 1d0f:ec20
> +-06.0 Device 1d0f:ec20
> +-07.0 Device 1d0f:ec20
> +-08.0 Device 1d0f:ec20
> +-09.0 Device 1d0f:ec20
> +-0a.0 Device 1d0f:ec20
> +-0b.0 Device 1d0f:ec20
> \-1f.0 XenSource, Inc. Xen Platform Device
> # dpdk-devbind.py -s
>
> Network devices using DPDK-compatible driver
> ============================================
> 0000:00:04.0 'Device ec20' drv=igb_uio unused=ena
> 0000:00:05.0 'Device ec20' drv=igb_uio unused=ena
> 0000:00:06.0 'Device ec20' drv=igb_uio unused=ena
> 0000:00:07.0 'Device ec20' drv=igb_uio unused=ena
> 0000:00:08.0 'Device ec20' drv=igb_uio unused=ena
> 0000:00:09.0 'Device ec20' drv=igb_uio unused=ena
> 0000:00:0a.0 'Device ec20' drv=igb_uio unused=ena
> 0000:00:0b.0 'Device ec20' drv=igb_uio unused=ena
>
> Network devices using kernel driver
> ===================================
> 0000:00:03.0 'Device ec20' if=nic0_0 drv=ena unused=igb_uio *Active*
next prev parent reply other threads:[~2019-06-07 0:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 21:26 Reeve Yang
2019-06-07 0:21 ` Reeve Yang [this message]
2019-06-07 10:37 ` Michał Krawczyk
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='CAGNTBAUP15fKb5cGKMDemnK-aAWGpkpNUQj64PifiNZ=7me00w@mail.gmail.com' \
--to=reeve.yang@gmail.com \
--cc=dev@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).