From: Ben Greear <greearb@candelatech.com>
To: Marc Haber <mh+linux-kernel@zugschlus.de>
Cc: linux-kernel@vger.kernel.org
Subject: Re: tulip and VLAN tagging - accepting larger frames without affecting higher layers?
Date: Sat, 13 Apr 2002 11:04:55 -0700 [thread overview]
Message-ID: <3CB87347.7000603@candelatech.com> (raw)
In-Reply-To: <E16veWm-00052F-00@janet.int.toplink-plannet.de> <20020411152327.GA600@stingr.net> <20020413135430.A5521@torres.ka0.zugschlus.de>
Marc Haber wrote:
> On Thu, Apr 11, 2002 at 07:23:27PM +0400, Paul P Komkoff Jr wrote:
>
>>It contains (following) (rediffed) working tulip mtu patch :)
>>
>
> That patch solved my problem.
>
> With that driver, the MTU still shows as 1500 bytes, while I thought
> that patch would cause the MTU to go up to 1504 bytes.
The ethX MTU should remain 1500 to not break non-vlan traffic. Secretly,
though, the NIC should pass frames that are 4 bytes bigger.
> Will this patch be in the mainstream kernel soon? Or could it have
> negative effects?
I wonder if we could somehow make the changes a module option even
if Jeff won't allow it in by default....
Most other drivers have the same issues....
Ben
>
> Greetings
> Marc
>
>
--
Ben Greear <greearb@candelatech.com> <Ben_Greear AT excite.com>
President of Candela Technologies Inc http://www.candelatech.com
ScryMUD: http://scry.wanfear.com http://scry.wanfear.com/~greear
prev parent reply other threads:[~2002-04-13 18:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 13:22 tulip and VLAN tagging - accepting larger frames without affecting higher layers? Marc Haber
2002-04-11 15:23 ` Paul P Komkoff Jr
2002-04-13 11:54 ` Marc Haber
2002-04-13 12:04 ` Paul P Komkoff Jr
2002-04-13 18:04 ` Ben Greear [this message]
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=3CB87347.7000603@candelatech.com \
--to=greearb@candelatech.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mh+linux-kernel@zugschlus.de \
/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