From: Ferruh Yigit <ferruh.yigit@intel.com>
To: Gaetan Rivet <grive@u256.net>, dev@dpdk.org
Cc: longli@microsoft.com, stable@dpdk.org
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH] net/failsafe: fix state synchro cleanup
Date: Tue, 13 Oct 2020 15:49:18 +0100 [thread overview]
Message-ID: <17ea8dd8-c747-8f4c-2337-c32ff7fe1ee0@intel.com> (raw)
In-Reply-To: <deb765fed1c11bcbbd5b9bf711852f24f456f5c7.1602512275.git.grive@u256.net>
On 10/12/2020 3:19 PM, Gaetan Rivet wrote:
> During a hotplug attempt, failsafe will try to bring a subdevice that
> just appeared to its internal state. On error, the subdevice is marked
> for removal and will be cleaned up.
>
> However failsafe_dev_remove() only remove active devices. Devices that
> failed during probe will be stuck in DEV_PARSED state repeatedly.
>
> Consider all devices when doing a removal round, but limit burst control
> and stats saving to active devices.
>
> Fixes: 598fb8aec6f6 ("net/failsafe: support device removal")
> Cc: stable@dpdk.org
> Signed-off-by: Gaetan Rivet <grive@u256.net>
Applied to dpdk-next-net/main, thanks.
prev parent reply other threads:[~2020-10-13 14:49 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-12 14:19 [dpdk-dev] " Gaetan Rivet
2020-10-13 14:49 ` Ferruh Yigit [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=17ea8dd8-c747-8f4c-2337-c32ff7fe1ee0@intel.com \
--to=ferruh.yigit@intel.com \
--cc=dev@dpdk.org \
--cc=grive@u256.net \
--cc=longli@microsoft.com \
--cc=stable@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).