From: Stephen Hemminger <stephen@networkplumber.org>
To: Wenbo Liu <liuwenbo109@gmail.com>
Cc: rasland@nvidia.com, dev@dpdk.org
Subject: Re: [PATCH] drivers/net/mlx5: fix mlx5 send packet failed
Date: Tue, 25 Mar 2025 07:10:03 -0700 [thread overview]
Message-ID: <20250325071003.11775779@hermes.local> (raw)
In-Reply-To: <1742899140-2013-1-git-send-email-liuwenbo109@gmail.com>
On Tue, 25 Mar 2025 18:39:00 +0800
Wenbo Liu <liuwenbo109@gmail.com> wrote:
> Test Environment: ARM architecture, OpenEuler operating system
> CPU: HUAWEI Kunpeng 920 5220, BIOS Vendor ID: HiSilicon
> Network Card: Mellanox Technologies MT27800 Family [ConnectX-5]
> DPDK program sending self-encapsulated packets with MAC, IP, and UDP headers
> continuously prints the following errors and ceases packet transmission
>
> mlx5_common: Failed to modify SQ using DevX
> mlx5_net: Cannot change the Tx SQ state to RESET Remote I/O error
>
> Signed-off-by: Wenbo Liu <liuwenbo109@gmail.com>
Patch has compile failures in CI and coding indent issue reported by checkpatch.
prev parent reply other threads:[~2025-03-25 14:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-25 10:39 Wenbo Liu
2025-03-25 14:10 ` Stephen Hemminger [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=20250325071003.11775779@hermes.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=liuwenbo109@gmail.com \
--cc=rasland@nvidia.com \
/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).