From: madhukar mythri <madhukar.mythri@gmail.com>
To: users@dpdk.org
Subject: [dpdk-users] Failed to bring-up DPDK ports on Azure VM
Date: Sun, 18 Apr 2021 17:51:09 +0530 [thread overview]
Message-ID: <CAAUNki0u1qovB4Gkf-5bVNncVSFdqmX2uDGiOYzALGkp7eqBAA@mail.gmail.com> (raw)
Hi,
When we tried to launch a DPDK app on Azure VM with 2-queues,
seeing following errors and thus we are not able to receive any traffic
on these NIC ports(MLX5).
On Azure VM, using "net_failsafe" PMD.
=======================
PORT 0 Max supports 16 rx queues and 16 tx queues (driver_name =
net_failsafe, driver_type = 16)
PORT 0 is polling for link-change, interrupts disabled
*rss_add_actions(): Failed to load BPF section l3_l4 (11): Resource
temporarily unavailable*
net_failsafe: Failed to create flow on sub_device 1
add_flow(): create() fails for port 0; Reason: action not supported
===================
This issue is seen with 2-queues only, whereas with 4-queues we are not
seeing this issue.
Does anybody faced similar issue and if any solution/work-around please let
me know.
DPDK version: 20.11
With RHEL: 7.9 version.
Thanks,
Madhukar.
next reply other threads:[~2021-04-18 12:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-18 12:21 madhukar mythri [this message]
2021-04-18 15:37 ` Stephen Hemminger
2021-04-19 6:28 ` madhukar mythri
2021-04-19 15:10 ` Stephen Hemminger
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=CAAUNki0u1qovB4Gkf-5bVNncVSFdqmX2uDGiOYzALGkp7eqBAA@mail.gmail.com \
--to=madhukar.mythri@gmail.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).