netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael Cronenworth <mike@cchtml.com>
To: netdev@vger.kernel.org
Subject: e1000e max frame calculation
Date: Mon, 06 Apr 2015 11:38:29 -0500	[thread overview]
Message-ID: <5522B685.2030104@cchtml.com> (raw)

Hello,

I have attempted to discuss this with upstream directly[1], but they will not 
respond to me. I will now attempt here.

The e1000e driver uses a different maximum frame calculation after a commit[2] in 
kernel 3.15. This caused everyone's setups that were using 9000 for MTU to break 
after they rebooted on their kernel update. The addition of the VLAN bytes force 
users to use 8996.

Other drivers appear to be using the "old" maximum frame calculation and can 
continue to use 9000.

Can a standard be decided upon that all drivers use or is it acceptable that one 
driver "does its own thing?"

Thanks,
Michael


[1] https://sourceforge.net/p/e1000/bugs/459/
[2] 
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/intel/e1000e/netdev.c?id=c751a3d58cf2dae89ec941a259025b0175d67b0c

             reply	other threads:[~2015-04-06 17:27 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-06 16:38 Michael Cronenworth [this message]
2015-04-06 18:38 ` e1000e max frame calculation 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
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=5522B685.2030104@cchtml.com \
    --to=mike@cchtml.com \
    --cc=netdev@vger.kernel.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).