From: Jacob Keller <jacob.e.keller@intel.com>
To: intel-wired-lan@osuosl.org
Subject: [Intel-wired-lan] [next-queue] fm10k: Correct MTU for jumbo frames
Date: Mon, 24 Aug 2015 17:01:59 -0700 [thread overview]
Message-ID: <1440460921-28318-2-git-send-email-jacob.e.keller@intel.com> (raw)
In-Reply-To: <1440460921-28318-1-git-send-email-jacob.e.keller@intel.com>
Based on hardware testing, the host interface can support up to 15368
bytes on the wire. Subtracting 8 for an internal switch tag and 14 for
the L2 header shows that the MTU should not be allowed to be set above
15346 bytes.
Signed-off-by: Matthew Vick <matthew.vick@intel.com>
Signed-off-by: Jacob Keller <jacob.e.keller@intel.com>
---
drivers/net/ethernet/intel/fm10k/fm10k.h | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/intel/fm10k/fm10k.h b/drivers/net/ethernet/intel/fm10k/fm10k.h
index 14440200499b..9e05a36783e5 100644
--- a/drivers/net/ethernet/intel/fm10k/fm10k.h
+++ b/drivers/net/ethernet/intel/fm10k/fm10k.h
@@ -33,7 +33,7 @@
#include "fm10k_pf.h"
#include "fm10k_vf.h"
-#define FM10K_MAX_JUMBO_FRAME_SIZE 15358 /* Maximum supported size 15K */
+#define FM10K_MAX_JUMBO_FRAME_SIZE 15346 /* Maximum supported size 15K */
#define MAX_QUEUES FM10K_MAX_QUEUES_PF
--
2.5.0.280.g4aaba03
next prev parent reply other threads:[~2015-08-25 0:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-25 0:01 [Intel-wired-lan] [next-queue] fm10k: use snprintf() instead of sprintf() to avoid buffer overflow Jacob Keller
2015-08-25 0:01 ` Jacob Keller [this message]
2015-08-25 0:02 ` [Intel-wired-lan] [next-queue] fm10k: do not use enum as boolean Jacob Keller
2015-09-30 19:05 ` Singh, Krishneil K
2015-08-25 0:02 ` [Intel-wired-lan] [next-queue] fm10k: do not assume VF always has 1 queue Jacob Keller
2015-08-26 16:44 ` [Intel-wired-lan] [next-queue] fm10k: use snprintf() instead of sprintf() to avoid buffer overflow Jesse Brandeburg
2015-08-26 16:46 ` Keller, Jacob E
2015-09-30 19:08 ` Singh, Krishneil K
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=1440460921-28318-2-git-send-email-jacob.e.keller@intel.com \
--to=jacob.e.keller@intel.com \
--cc=intel-wired-lan@osuosl.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