From: Alban <albeu@free.fr>
To: Ben Hutchings <ben@decadent.org.uk>
Cc: Aban Bedel <albeu@free.fr>,
linux-kernel@vger.kernel.org, netdev@vger.kernel.org,
Bjorn Helgaas <bhelgaas@google.com>,
Benoit Taine <benoit.taine@lip6.fr>,
"Eric W. Biederman" <ebiederm@xmission.com>,
"David S. Miller" <davem@davemloft.net>
Subject: Re: [PATCH 1/2] 8139too: Allow setting MTU larger than 1500
Date: Fri, 21 Nov 2014 14:58:53 +0100 [thread overview]
Message-ID: <20141121145853.1be898de@tock> (raw)
In-Reply-To: <1416530074.7215.11.camel@decadent.org.uk>
On Fri, 21 Nov 2014 00:34:34 +0000
Ben Hutchings <ben@decadent.org.uk> wrote:
> On Sat, 2014-11-08 at 12:48 +0100, Alban Bedel wrote:
> > Replace the default ndo_change_mtu callback with one that allow
> > setting MTU that the driver can handle.
> >
> > Signed-off-by: Alban Bedel <albeu@free.fr>
> > ---
> > drivers/net/ethernet/realtek/8139too.c | 13 ++++++++++++-
> > 1 file changed, 12 insertions(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/ethernet/realtek/8139too.c
> > b/drivers/net/ethernet/realtek/8139too.c index 007b38c..8387de9
> > 100644 --- a/drivers/net/ethernet/realtek/8139too.c
> > +++ b/drivers/net/ethernet/realtek/8139too.c
> > @@ -185,6 +185,9 @@ static int debug = -1;
> > /* max supported ethernet frame size -- must be at least
> > (dev->mtu+14+4).*/ #define MAX_ETH_FRAME_SIZE 1536
> >
> > +/* max supported payload size */
> > +#define MAX_ETH_DATA_SIZE (MAX_ETH_FRAME_SIZE - ETH_HLEN -
> > ETH_FCS_LEN)
> [...]
>
> Does this maximum still allow for VLAN tags, or should it use
> VLAN_ETH_HLEN instead of ETH_HLEN?
That might well be as the VLAN code seems to assume that the physical
device can handle frames of MTU + VLAN_HLEN bytes. I can fix it, but to
me it seems like the VLAN code should be fixed to respect the physical
device MTU.
Alban
next prev parent reply other threads:[~2014-11-21 13:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-08 11:48 [PATCH 1/2] 8139too: Allow setting MTU larger than 1500 Alban Bedel
2014-11-08 11:48 ` [PATCH 2/2] 8139too: Allow using the largest possible MTU Alban Bedel
2014-11-10 20:30 ` David Miller
2014-11-10 20:30 ` [PATCH 1/2] 8139too: Allow setting MTU larger than 1500 David Miller
2014-11-21 0:34 ` Ben Hutchings
2014-11-21 13:58 ` Alban [this message]
2014-11-21 18:51 ` Ben Hutchings
2014-11-21 18:57 ` Alban
2014-11-23 2:42 ` Ben Hutchings
-- strict thread matches above, loose matches on Subject: below --
2013-11-17 13:05 Alban Bedel
2013-11-18 20:50 ` David Miller
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=20141121145853.1be898de@tock \
--to=albeu@free.fr \
--cc=ben@decadent.org.uk \
--cc=benoit.taine@lip6.fr \
--cc=bhelgaas@google.com \
--cc=davem@davemloft.net \
--cc=ebiederm@xmission.com \
--cc=linux-kernel@vger.kernel.org \
--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.