From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 713] Cannot init ENA port in skeleton example
Date: Tue, 18 May 2021 10:54:37 +0000 [thread overview]
Message-ID: <bug-713-3-xvZEhUIHjG@http.bugs.dpdk.org/> (raw)
In-Reply-To: <bug-713-3@http.bugs.dpdk.org/>
https://bugs.dpdk.org/show_bug.cgi?id=713
kalyan (kaprakashr@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
Resolution|--- |WORKSFORME
Status|UNCONFIRMED |RESOLVED
--- Comment #2 from kalyan (kaprakashr@gmail.com) ---
Hi David,
Thanks much! After I masked that check it works(snapshot below),
Besides, could you throw some light on the future implications of masking this
check in AWS ENA? (And also the reason behind introducing this check)
__Snap shot__
oot@ip-172-31-23-251:/home/ubuntu/dpdk-stable-20.11.1/build/examples#
./dpdk-skeleton -l 1 -n 2
EAL: Detected 4 lcore(s)
EAL: Detected 1 NUMA nodes
EAL: Detected static linkage of DPDK
EAL: Multi-process socket /var/run/dpdk/rte/mp_socket
EAL: Selected IOVA mode 'PA'
EAL: No available hugepages reported in hugepages-1048576kB
EAL: Probing VFIO support...
EAL: Invalid NUMA socket, default to 0
EAL: Invalid NUMA socket, default to 0
EAL: Probe PCI driver: net_ena (1d0f:ec20) device: 0000:00:06.0 (socket 0)
EAL: Invalid NUMA socket, default to 0
EAL: Probe PCI driver: net_ena (1d0f:ec20) device: 0000:00:07.0 (socket 0)
EAL: No legacy callbacks, legacy socket not created
Port 0 MAC: 06 66 dc 11 e8 30
Port 1 MAC: 06 b7 8f e2 7e 6e
Core 1 forwarding packets.
Thanks,
Kalyan
--
You are receiving this mail because:
You are the assignee for the bug.
prev parent reply other threads:[~2021-05-18 10:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-18 9:43 [dpdk-dev] [Bug 713] Failure in latest DPDK build: Cannot init any port in AWS ENA bugzilla
2021-05-18 10:54 ` bugzilla [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=bug-713-3-xvZEhUIHjG@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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).