[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <41b516cb0709211427s45cdd3b0pa0bb76d114d5f041@mail.gmail.com>
Date: Fri, 21 Sep 2007 14:27:11 -0700
From: "Chris Leech" <chris.leech@...il.com>
To: hadi@...erus.ca
Cc: "Ben Greear" <greearb@...delatech.com>,
"Emil Micek" <emil.micek@...jasek.cz>,
"auke-jan.h.kok@...el.com" <auke-jan.h.kok@...el.com>,
"netdev mailing list" <netdev@...r.kernel.org>,
Jesse <jesse.brandeburg@...el.com>
Subject: Re: change the way e1000 is handling short VLAN frames
On 9/21/07, jamal <hadi@...erus.ca> wrote:
> On Fri, 2007-21-09 at 08:43 -0700, Ben Greear wrote:
>
> > I just re-read the spec, and a bridge *may* pad up to 68, but it is not
> > required.
> > On page 166, it says equipment must be able to handle 64 byte minimums.
> >
> > See page 22 (section 7.2) of this document:
> >
> > http://standards.ieee.org/getieee802/download/802.1Q-1998.pdf
> >
> > Also, page 63, 165, 166
>
> Thanks for the enlightnment.
> Do we need an ethtool interface to turn off hardware accelerated vlans?
> Jesse is indicating that the intel hardware can only handle the MUST but
> not the SHOULD of the spec.
> Actually a more basic question: Can you select one or the other mode in
> the software based vlans?
Inserting the VLAN tag in software will not change the behavior in the
way you want anyway, short frames will still be padded to 64 bytes.
You'd have to do short packet padding in software to 68 bytes. Or do
software padding to 64 bytes and let the hardware insert the VLAN tag
after.
Chris
-
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists