All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alexander Duyck <alexander.duyck@gmail.com>
To: Hisashi T Fujinaka <htodd@twofifty.com>,
	Alexander Duyck <alexander.h.duyck@redhat.com>
Cc: Michael Cronenworth <mike@cchtml.com>, netdev@vger.kernel.org
Subject: Re: e1000e max frame calculation
Date: Wed, 08 Apr 2015 10:17:27 -0700	[thread overview]
Message-ID: <552562A7.8090307@gmail.com> (raw)
In-Reply-To: <alpine.NEB.2.11.1504062043320.2726@chris.i8u.org>

On 04/06/2015 08:47 PM, Hisashi T Fujinaka wrote:
> On Mon, 6 Apr 2015, Alexander Duyck wrote:
>
>> The e1000e pch parts seem very limited in terms of their jumbo frames
>> support.  It looks like the first pch part only supported 4K, and in
>> the case of the later generations I only see support for a 9018 jumbo
>> frame listed in the datasheet.  I suspect this is why that is set as
>> the limit in the driver. The question at this point is if 9018 is the
>> limit, why is it the limit and is there any wiggle room to it.
>
> It's a limit that was told to us by the HW group for the 82579.

The question I have is if the limit of 9018 includes the VLAN header or
not.  The reason why I ask is that prior to 3.15 you could configure an
MTU of 9000, and then still enable VLANs which would push the upper size
to a theoretical limit of 9022.

For example, what is the upper limit on the Windows driver for this
part?  Does it not support a jumbo frame size of 9014 (Excluding the CRC
and VLAN header)?  If so we could probably increase the value to 9022 in
these drivers, not suffer any ill effects, and resolve the issue that
Michael has been having after the change to include the VLAN_HLEN on the
max frame size calculation.

- Alex

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

Thread overview: 36+ 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 18:38   ` [Intel-wired-lan] " 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 [this message]
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:02             ` [Intel-wired-lan] " Alexander Duyck
2015-04-08 21:15             ` Hisashi T Fujinaka
2015-04-08 21:15               ` [Intel-wired-lan] " Hisashi T Fujinaka
2015-04-08 22:58               ` Alexander Duyck
2015-04-08 22:58                 ` [Intel-wired-lan] " Alexander Duyck
2015-04-08 23:05                 ` Hisashi T Fujinaka
2015-04-08 23:05                   ` [Intel-wired-lan] " Hisashi T Fujinaka
2015-04-08 23:13                   ` Alexander Duyck
2015-04-08 23:13                     ` [Intel-wired-lan] " Alexander Duyck
2015-04-09  0:10                     ` Hisashi T Fujinaka
2015-04-09  0:10                       ` [Intel-wired-lan] " Hisashi T Fujinaka
2015-04-09  0:26                       ` Hisashi T Fujinaka
2015-04-09  0:26                         ` [Intel-wired-lan] " Hisashi T Fujinaka
2015-04-09  1:19                         ` Alexander Duyck
2015-04-09  1:19                           ` [Intel-wired-lan] " Alexander Duyck
2015-04-09  6:17                           ` Templeman, Chaim
2015-04-09  6:17                             ` Templeman, Chaim
2015-04-09 15:51                             ` Alexander Duyck
2015-04-09 15:51                               ` Alexander Duyck
2015-04-13 18:26                               ` Templeman, Chaim
2015-04-13 18:26                                 ` Templeman, Chaim
2015-04-09  0:01             ` Jeff Kirsher
2015-04-09  0:01               ` [Intel-wired-lan] " Jeff Kirsher
2015-04-09  4:48             ` Michael Cronenworth
2015-04-09  4:48               ` [Intel-wired-lan] " Michael Cronenworth
2015-04-21  2:38             ` Brown, Aaron F
2015-04-21  2:38               ` 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=552562A7.8090307@gmail.com \
    --to=alexander.duyck@gmail.com \
    --cc=alexander.h.duyck@redhat.com \
    --cc=htodd@twofifty.com \
    --cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.