From: Ben Greear <greearb@candelatech.com>
To: Rask Ingemann Lambertsen <rask@sygehus.dk>
Cc: netdev@oss.sgi.com, jgarzik@pobox.com
Subject: Re: [EXPERIMENTAL PATCH] 2.4 tulip jumbo frames
Date: Fri, 19 Dec 2003 22:22:34 -0800 [thread overview]
Message-ID: <3FE3EAAA.6020608@candelatech.com> (raw)
In-Reply-To: <20031219153242.B1390@sygehus.dk>
Rask Ingemann Lambertsen wrote:
> On Wed, Dec 10, 2003 at 12:40:02AM +0100, Rask Ingemann Lambertsen wrote:
>
>
>>That said, even checking CONFIG_VLAN_8021Q is probably flawed too, because
>>ideally, even when building a kernel without VLAN support, you should be able
>>to use the bridging support in a VLAN environment. IMHO. I mean, if this is
>>not the case, please remind me why we need VLAN patches in the first place
>>since setting an MTU of 1496 bytes works with every Ethernet board and driver.
>
>
> Further, why is it not the responsibility of vconfig to ensure that the MTU
> of the VLAN device is 4 lower than that of the underlying, "bare" Ethernet
> device?
Because correctly patched drivers can have eth0 with MTU 1500 and vlan eth0.5 with
MTU of 1500 as well. I do not want to add artificial policy in vconfig or the
kernel,though of course users can hack up the MTU settings manually as
desired...
Ben
--
Ben Greear <greearb@candelatech.com> <Ben_Greear@excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
next prev parent reply other threads:[~2003-12-20 6:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-09 15:06 [EXPERIMENTAL PATCH] 2.4 tulip jumbo frames Rask Ingemann Lambertsen
2003-12-09 16:45 ` Jeff Garzik
2003-12-09 21:32 ` Rask Ingemann Lambertsen
2003-12-09 22:38 ` Ben Greear
2003-12-09 23:40 ` Rask Ingemann Lambertsen
2003-12-19 14:32 ` Rask Ingemann Lambertsen
2003-12-20 6:22 ` Ben Greear [this message]
2003-12-13 17:29 ` Rask Ingemann Lambertsen
2004-05-27 19:29 ` Ben Greear
2003-12-09 17:28 ` Ben Greear
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=3FE3EAAA.6020608@candelatech.com \
--to=greearb@candelatech.com \
--cc=jgarzik@pobox.com \
--cc=netdev@oss.sgi.com \
--cc=rask@sygehus.dk \
/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).