DPDK usage discussions
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: madhukar mythri <madhukar.mythri@gmail.com>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] Failed to bring-up DPDK ports on Azure VM
Date: Sun, 18 Apr 2021 08:37:53 -0700
Message-ID: <20210418083753.308083bc@hermes.local> (raw)
In-Reply-To: <CAAUNki0u1qovB4Gkf-5bVNncVSFdqmX2uDGiOYzALGkp7eqBAA@mail.gmail.com>

On Sun, 18 Apr 2021 17:51:09 +0530
madhukar mythri <madhukar.mythri@gmail.com> wrote:

> 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.


If you are using failsafe, make sure that you have the Mellanox drivers enabled
in your DPDK build, also TAP device. You need to build with rdma-core version 23 or
later, and you need to have the kernel modules for flower, multiq, and TAP.

Turn on full DPDK logging and check the kernel log (dmesg).

  reply	other threads:[~2021-04-18 15:38 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-18 12:21 madhukar mythri
2021-04-18 15:37 ` Stephen Hemminger [this message]
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=20210418083753.308083bc@hermes.local \
    --to=stephen@networkplumber.org \
    --cc=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

DPDK usage discussions

This inbox may be cloned and mirrored by anyone:

	git clone --mirror https://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ https://inbox.dpdk.org/users \
		users@dpdk.org
	public-inbox-index users

Example config snippet for mirrors.
Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git