Re: PATCH: VLAN support for 3c59x/3c90x

[Ben Greear]

Willy Tarreau wrote:
> Hi Ben,
>
> On Sat, Jul 31, 2004 at 10:03:31AM -0700, Ben Greear wrote:
>  
>
> > VLAN allows you to continue using the ethX interface as a regular
> > ethernet interface, so you do not generally want it's MTU to be set
> > to 1504 because then the other peer ethernet interfaces would also
> > have to be set to 1504.  I believe it is much better to silently let
> > the extra 4 bytes pass but NOT advertise this extra 4 bytes to
> > anything that actually cares about MTU.
>
>
> I 100% agree with you on this one, but I don't see how playing with
> change_mtu() would change anything. Ideally, we would need to export
> the level 2 limit (imposed by hardware and intermediate switches) to
> other drivers such as 802_1q, and let only the IP stack rely on dev->mtu.

Ok, I agree that it would be good to have a hard limit exported.
I am less certain that VLAN should modify any MTU based on this
information, but at the very least, it could warn the user that
some action needs to be taken and let the user make an informed
decision.

Also, it seems that most (all?) ethernet chips can handle the extra
4 bytes, but the patches are varying degrees of ugliness and so
many have not made it into the kernel proper.


> I've seen several drivers which silently add 4 bytes to the hardware
> config when CONFIG_VLAN is set. I find it better than fooling the IP
> stack into using 1504 bytes, which is a disaster on UDP !

It would be a disaster with any IP protocol, not just UDP.

Ben

--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc  http://www.candelatech.com

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/