From: Stephen Hemminger <stephen@networkplumber.org>
To: dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH 0/3] fix error path of multi-process probe
Date: Wed, 14 Jun 2023 12:39:49 -0700 [thread overview]
Message-ID: <20230614123949.06da4bc9@hermes.local> (raw)
In-Reply-To: <20190302024253.15594-1-thomas@monjalon.net>
On Sat, 2 Mar 2019 03:42:50 +0100
Thomas Monjalon <thomas@monjalon.net> wrote:
> While working on multi-process support of failsafe with Raslan,
> some issues have been discovered on probing failures.
>
> Thomas Monjalon (3):
> eal: remove useless checks for already probed device
> eal: remove error logs for already probed device
> eal: fix multi-process probe failure handling
>
> lib/librte_eal/common/eal_common_dev.c | 31 ++++++++++----------------
> lib/librte_eal/common/eal_private.h | 2 +-
> lib/librte_eal/common/hotplug_mp.c | 14 +++++++-----
> 3 files changed, 21 insertions(+), 26 deletions(-)
>
Is this old patch set relevant. Seems like it addressing a
"this should never happen but if it does don't be stupid" kind of scenario.
Marking it as "Changes Requested" since rebase and retest would be needed.
prev parent reply other threads:[~2023-06-14 19:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-02 2:42 Thomas Monjalon
2019-03-02 2:42 ` [dpdk-dev] [PATCH 1/3] eal: remove useless checks for already probed device Thomas Monjalon
2019-03-13 13:46 ` Zhang, Qi Z
2023-06-11 2:52 ` Stephen Hemminger
2019-03-02 2:42 ` [dpdk-dev] [PATCH 2/3] eal: remove error logs " Thomas Monjalon
2019-03-02 2:42 ` [dpdk-dev] [PATCH 3/3] eal: fix multi-process probe failure handling Thomas Monjalon
2019-03-14 7:15 ` Zhang, Qi Z
2019-03-14 7:15 ` Zhang, Qi Z
2023-06-14 19:39 ` 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=20230614123949.06da4bc9@hermes.local \
--to=stephen@networkplumber.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).