From: Stephen Hemminger <stephen@networkplumber.org>
To: Maayan Kashani <mkashani@nvidia.com>
Cc: <dev@dpdk.org>, <dsosnowski@nvidia.com>, <rasland@nvidia.com>,
"Aman Singh" <aman.deep.singh@intel.com>,
Yuying Zhang <yuying.zhang@intel.com>
Subject: Re: [PATCH] app/testpmd: support retrying device stop
Date: Mon, 3 Jun 2024 10:09:31 -0700 [thread overview]
Message-ID: <20240603100931.5195595b@hermes.local> (raw)
In-Reply-To: <20240602103035.197205-1-mkashani@nvidia.com>
On Sun, 2 Jun 2024 13:30:35 +0300
Maayan Kashani <mkashani@nvidia.com> wrote:
> From: Dariusz Sosnowski <dsosnowski@nvidia.com>
>
> In some cases rte_eth_dev_stop() can fail with EBUSY error code meaning
> that port cannot be stopped, because of other resources referencing this
> port and port must be stopped again after these resources are freed.
>
> This patch adds handling of EBUSY error code on port stop to testpmd.
>
> Signed-off-by: Dariusz Sosnowski <dsosnowski@nvidia.com>
What causes EBUSY. Seems like a driver bug or a test scenario problem.
You can't expect every DPDK application to retry.
prev parent reply other threads:[~2024-06-03 17:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-02 10:30 Maayan Kashani
2024-06-03 17:09 ` 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=20240603100931.5195595b@hermes.local \
--to=stephen@networkplumber.org \
--cc=aman.deep.singh@intel.com \
--cc=dev@dpdk.org \
--cc=dsosnowski@nvidia.com \
--cc=mkashani@nvidia.com \
--cc=rasland@nvidia.com \
--cc=yuying.zhang@intel.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).