From: Wenzhuo Lu <wenzhuo.lu@intel.com>
To: dev@dpdk.org
Cc: Wenzhuo Lu <wenzhuo.lu@intel.com>
Subject: [dpdk-dev] [PATCH v2 2/2] doc: announce ixgbe MTU setting limitation
Date: Thu, 9 Feb 2017 09:28:00 +0800 [thread overview]
Message-ID: <1486603680-62864-3-git-send-email-wenzhuo.lu@intel.com> (raw)
In-Reply-To: <1486603680-62864-1-git-send-email-wenzhuo.lu@intel.com>
Signed-off-by: Wenzhuo Lu <wenzhuo.lu@intel.com>
---
doc/guides/nics/ixgbe.rst | 9 +++++++++
1 file changed, 9 insertions(+)
diff --git a/doc/guides/nics/ixgbe.rst b/doc/guides/nics/ixgbe.rst
index 05ecc2a..aceeb13 100644
--- a/doc/guides/nics/ixgbe.rst
+++ b/doc/guides/nics/ixgbe.rst
@@ -233,6 +233,15 @@ be calculated as follows:
In order to ensure valid results, it is recommended to poll every 4 minutes.
+MTU setting
+~~~~~~~~~~~
+
+Although the user can set the MTU separately on PF and VF ports, the ixgbe NIC
+only supports one global MTU per physical port.
+So when the user sets different MTUs on PF and VF ports in one physical port,
+the real MTU for all these PF and VF ports is the largest value set.
+This behavior is based on the kernel driver behavior.
+
Supported Chipsets and NICs
---------------------------
--
1.9.3
next prev parent reply other threads:[~2017-02-09 1:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-07 6:22 [dpdk-dev] [PATCH] " Wenzhuo Lu
2017-02-08 16:12 ` Ferruh Yigit
2017-02-09 0:40 ` Lu, Wenzhuo
2017-02-08 17:10 ` Mcnamara, John
2017-02-09 0:42 ` Lu, Wenzhuo
2017-02-09 1:27 ` [dpdk-dev] [PATCH v2 0/2] update ixgbe doc Wenzhuo Lu
2017-02-09 1:27 ` [dpdk-dev] [PATCH v2 1/2] doc: fix framework of " Wenzhuo Lu
2017-02-09 15:05 ` [dpdk-dev] [dpdk-stable] " Mcnamara, John
2017-02-09 1:28 ` Wenzhuo Lu [this message]
2017-02-09 15:05 ` [dpdk-dev] [PATCH v2 2/2] doc: announce ixgbe MTU setting limitation Mcnamara, John
2017-02-09 15:28 ` [dpdk-dev] [PATCH v2 0/2] update ixgbe doc Ferruh Yigit
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=1486603680-62864-3-git-send-email-wenzhuo.lu@intel.com \
--to=wenzhuo.lu@intel.com \
--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).