From: Gaetan Rivet <grive@u256.net>
To: dev@dpdk.org
Cc: stable@dpdk.org
Subject: [dpdk-dev] [PATCH v1 2/2] doc/failsafe: fix incorrect statement regarding number of sub-device
Date: Sat, 22 Feb 2020 01:14:40 +0100 [thread overview]
Message-ID: <6a49dddd485cb1a133e9f100fba68341d575254e.1582330416.git.grive@u256.net> (raw)
In-Reply-To: <cover.1582330416.git.grive@u256.net>
Supporting more than 2 sub-device is a remnant from earlier fail-safe
design, that was never actually published.
Fixes: a46f8d584eb8 ("net/failsafe: add fail-safe PMD")
Cc: stable@dpdk.org
Signed-off-by: Gaetan Rivet <grive@u256.net>
---
doc/guides/nics/fail_safe.rst | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/doc/guides/nics/fail_safe.rst b/doc/guides/nics/fail_safe.rst
index 3ce2f8bee..b4a92f663 100644
--- a/doc/guides/nics/fail_safe.rst
+++ b/doc/guides/nics/fail_safe.rst
@@ -49,7 +49,7 @@ The Fail-safe PMD can be used like most other DPDK virtual devices, by passing a
``--vdev`` parameter to the EAL when starting the application. The device name
must start with the *net_failsafe* prefix, followed by numbers or letters. This
name must be unique for each device. Each fail-safe instance must have at least one
-sub-device, up to ``RTE_MAX_ETHPORTS-1``.
+sub-device, and at most two.
A sub-device can be any DPDK device, including possibly another fail-safe device.
--
2.25.0
prev parent reply other threads:[~2020-02-22 0:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-22 0:14 [dpdk-dev] [PATCH v1 0/2] failsafe: improve documentation Gaetan Rivet
2020-02-22 0:14 ` [dpdk-dev] [PATCH v1 1/2] doc/failsafe: improve fail-safe documentation Gaetan Rivet
2020-02-27 17:46 ` Ferruh Yigit
2020-03-03 16:30 ` Kovacevic, Marko
2020-03-04 16:41 ` Ferruh Yigit
2020-02-22 0:14 ` Gaetan Rivet [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=6a49dddd485cb1a133e9f100fba68341d575254e.1582330416.git.grive@u256.net \
--to=grive@u256.net \
--cc=dev@dpdk.org \
--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).