From: Alexander Duyck <alexander.duyck@gmail.com>
To: "Templeman, Chaim" <chaim.templeman@intel.com>,
Hisashi T Fujinaka <htodd@twofifty.com>
Cc: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"mike@cchtml.com" <mike@cchtml.com>,
"intel-wired-lan@lists.osuosl.org"
<intel-wired-lan@lists.osuosl.org>,
"Ertman, David M" <david.m.ertman@intel.com>,
"Lubetkin, YanirX" <yanirx.lubetkin@intel.com>
Subject: Re: [Intel-wired-lan] [PATCH] e1000e: Cleanup handling of VLAN_HLEN as a part of max frame size
Date: Thu, 09 Apr 2015 08:51:18 -0700 [thread overview]
Message-ID: <55269FF6.4090003@gmail.com> (raw)
In-Reply-To: <BD4006F19E8FC247A4760EC0EE12CCDF468ACD40@HASMSX110.ger.corp.intel.com>
On 04/08/2015 11:17 PM, Templeman, Chaim wrote:
> We will look into this with the HW architect and get back to you on what the HW limitations actually are on this issue.
Chaim, thanks for looking into this. The key piece that would be useful
to know is if the 9018 should really be 9022 if you account for both
VLAN header and CRC. Based on the documentation for the Windows driver
that seems to be the case as they support an MTU of 9014 excluding the 8
bytes for CRC and VLAN header.
- Alex
next prev parent reply other threads:[~2015-04-09 15:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-06 16:38 e1000e max frame calculation Michael Cronenworth
2015-04-06 18:38 ` Alexander Duyck
2015-04-06 21:45 ` Michael Cronenworth
2015-04-06 23:17 ` Alexander Duyck
2015-04-07 3:47 ` Hisashi T Fujinaka
2015-04-08 17:17 ` Alexander Duyck
2015-04-08 17:25 ` Hisashi T Fujinaka
2015-04-08 21:02 ` [PATCH] e1000e: Cleanup handling of VLAN_HLEN as a part of max frame size Alexander Duyck
2015-04-08 21:15 ` Hisashi T Fujinaka
2015-04-08 22:58 ` Alexander Duyck
2015-04-08 23:05 ` Hisashi T Fujinaka
2015-04-08 23:13 ` Alexander Duyck
2015-04-09 0:10 ` Hisashi T Fujinaka
2015-04-09 0:26 ` Hisashi T Fujinaka
2015-04-09 1:19 ` Alexander Duyck
2015-04-09 6:17 ` [Intel-wired-lan] " Templeman, Chaim
2015-04-09 15:51 ` Alexander Duyck [this message]
2015-04-13 18:26 ` Templeman, Chaim
2015-04-09 0:01 ` Jeff Kirsher
2015-04-09 4:48 ` Michael Cronenworth
2015-04-21 2:38 ` [Intel-wired-lan] " Brown, Aaron F
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=55269FF6.4090003@gmail.com \
--to=alexander.duyck@gmail.com \
--cc=chaim.templeman@intel.com \
--cc=david.m.ertman@intel.com \
--cc=htodd@twofifty.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=mike@cchtml.com \
--cc=netdev@vger.kernel.org \
--cc=yanirx.lubetkin@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).