patches for DPDK stable branches
 help / color / mirror / Atom feed
From: Mingjin Ye <mingjinx.ye@intel.com>
To: dev@dpdk.org
Cc: qiming.yang@intel.com, stable@dpdk.org, yidingx.zhou@intel.com,
	Mingjin Ye <mingjinx.ye@intel.com>,
	Wenjun Wu <wenjun1.wu@intel.com>
Subject: [PATCH v3] doc: comment VF does not support multi-process
Date: Tue, 16 May 2023 10:22:05 +0000	[thread overview]
Message-ID: <20230516102205.537013-1-mingjinx.ye@intel.com> (raw)
In-Reply-To: <20230506100252.215680-1-mingjinx.ye@intel.com>

Announcing that multi-process is not supported

Signed-off-by: Mingjin Ye <mingjinx.ye@intel.com>
---
v2: Modify issue description reason.
---
V3: Modify description.
---
 doc/guides/nics/ixgbe.rst | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/doc/guides/nics/ixgbe.rst b/doc/guides/nics/ixgbe.rst
index b1d77ab7ab..816d614c33 100644
--- a/doc/guides/nics/ixgbe.rst
+++ b/doc/guides/nics/ixgbe.rst
@@ -461,3 +461,9 @@ show bypass config
 Show the bypass configuration for a bypass enabled NIC using the lowest port on the NIC::
 
    testpmd> show bypass config (port_id)
+
+VF driver does not support multi-process
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+The VF driver does not support multi-process. And some function pointers
+in the case of multi-process are not set correctly.
-- 
2.25.1


  parent reply	other threads:[~2023-05-16 10:28 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230420061429.140113-1-mingjinx.ye@intel.com>
2023-05-06 10:02 ` [PATCH v2] doc: add PMD known issue Mingjin Ye
2023-05-15  5:56   ` Zhang, Qi Z
2023-05-16 10:22   ` Mingjin Ye [this message]
2023-05-16 15:18     ` [PATCH v3] doc: comment VF does not support multi-process Stephen Hemminger
2023-05-17  2:29       ` Ye, MingjinX
2023-05-17 10:03     ` [PATCH v4] doc: update ixgbe VF features list Mingjin Ye
2023-05-18  8:25       ` Zhang, Qi Z

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=20230516102205.537013-1-mingjinx.ye@intel.com \
    --to=mingjinx.ye@intel.com \
    --cc=dev@dpdk.org \
    --cc=qiming.yang@intel.com \
    --cc=stable@dpdk.org \
    --cc=wenjun1.wu@intel.com \
    --cc=yidingx.zhou@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).