From: Marvin Liu <yong.liu@intel.com>
To: thomas@monjalon.net
Cc: dev@dpdk.org, Marvin Liu <yong.liu@intel.com>
Subject: [dpdk-dev] [PATCH] Doc: add known issue for restricted vdev ethdev ops in secondary process
Date: Wed, 31 Oct 2018 22:49:07 +0800 [thread overview]
Message-ID: <20181031144907.303203-1-yong.liu@intel.com> (raw)
Signed-off-by: Marvin Liu <yong.liu@intel.com>
diff --git a/doc/guides/rel_notes/known_issues.rst b/doc/guides/rel_notes/known_issues.rst
index 95e4ce693..617255cd7 100644
--- a/doc/guides/rel_notes/known_issues.rst
+++ b/doc/guides/rel_notes/known_issues.rst
@@ -759,3 +759,21 @@ Netvsc driver and application restart
**Driver/Module**:
``uio_hv_generic`` module.
+
+
+Restricted vdev ethdev operations supported in secondary process
+----------------------------------------------------------------
+**Description**
+ In current virtual device sharing model, Ethernet device data structure will be
+ shared between primary and secondary process. Only those Ethernet device operations
+ which based on it are workable in secondary process.
+
+**Implication**
+ Some Ethernet device operations like device start/stop will be failed on virtual
+ device in secondary process.
+
+**Affected Environment/Platform**:
+ ALL.
+
+**Driver/Module**:
+ Virtual Device Poll Mode Driver (PMD).
--
2.14.1
next reply other threads:[~2018-10-31 7:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 14:49 Marvin Liu [this message]
2018-10-31 8:22 ` [dpdk-dev] Question about jumbo frame support on ixgbe Hideyuki Yamashita
2018-10-31 15:48 ` Stephen Hemminger
2018-11-01 3:27 ` Zhao1, Wei
2018-11-01 6:55 ` Zhao1, Wei
2018-11-01 3:10 ` Zhao1, Wei
2018-11-02 1:38 ` Hideyuki Yamashita
2018-11-05 9:47 ` Zhao1, Wei
2018-11-01 3:12 ` Zhao1, Wei
2018-11-22 18:07 ` [dpdk-dev] [PATCH] Doc: add known issue for restricted vdev ethdev ops in secondary process Mcnamara, John
2018-11-23 2:07 ` Thomas Monjalon
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=20181031144907.303203-1-yong.liu@intel.com \
--to=yong.liu@intel.com \
--cc=dev@dpdk.org \
--cc=thomas@monjalon.net \
/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).