From: Ben Greear <greearb@candelatech.com>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Johannes Erdfelt <johannes@erdfelt.com>, netdev@oss.sgi.com
Subject: Re: [RFC] tulip VLAN support
Date: Wed, 05 Jan 2005 14:56:19 -0800 [thread overview]
Message-ID: <41DC7093.2080705@candelatech.com> (raw)
In-Reply-To: <41DC6E08.3080507@pobox.com>
> What size do you need? 1504 bytes, right?
1500 MTU + 14 for header + 4 for CRC + 4 for VLAN == 1522
Normally, you just have to tell the chip to accept slightly larger frames
and/or ignore the over-size frame flag. You do not actually need any ability
to set a larger than 1500 MTU.
Ben
--
Ben Greear <greearb@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2005-01-05 22:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-05 19:34 [RFC] tulip VLAN support Johannes Erdfelt
2005-01-05 22:12 ` Jeff Garzik
2005-01-05 22:17 ` Ben Greear
2005-01-05 22:31 ` Johannes Erdfelt
2005-01-05 22:45 ` Jeff Garzik
2005-01-05 22:56 ` 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=41DC7093.2080705@candelatech.com \
--to=greearb@candelatech.com \
--cc=jgarzik@pobox.com \
--cc=johannes@erdfelt.com \
--cc=netdev@oss.sgi.com \
/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).