From: Rask Ingemann Lambertsen <rask@sygehus.dk>
To: netdev@oss.sgi.com
Subject: Re: network interface cards native vlans support in linux kernel?
Date: Wed, 12 Nov 2003 20:48:04 +0100 [thread overview]
Message-ID: <20031112204804.B968@sygehus.dk> (raw)
In-Reply-To: <3F96B7FD.7080607@candelatech.com>; from greearb@candelatech.com on Wed, Oct 22, 2003 at 10:01:49AM -0700
On Wed, Oct 22, 2003 at 10:01:49AM -0700, Ben Greear wrote:
> Rask Ingemann Lambertsen wrote:
> >
> > What does a driver need to do to make sure it can handle vlan frames? Is it
> > enought to be prepared to handle frames of size dev->mtu+4? How do I know 4
> > bytes will be enough tomorrow when someone introduces VLAN2 with a 64-bit tag?
> > Checking for CONFIG_VLAN is of no use, right?
>
> It needs to be able to handle 1518 bytes (+crc), send and receive. I'd
> suggest using the Intel e100 or e1000, as they both support VLANs just fine.
> Most other GigE nics work too.
I was thinking about what to do as a driver *writer* rather than as a driver
*user*.
#include <linux/if_vlan.h>
and allocating buffers of (dev->mtu + VLAN_ETH_HLEN) bytes. Some chips, such
as the Tulip series, need an extra 4 bytes for the CRC when receiving.
--
Regards,
Rask Ingemann Lambertsen
next prev parent reply other threads:[~2003-11-12 19:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-09 15:19 network interface cards native vlans support in linux kernel? Andrius Kasparavicius
2003-07-09 15:28 ` Jeff Garzik
2003-09-11 14:57 ` Rask Ingemann Lambertsen
2003-10-22 12:06 ` Rask Ingemann Lambertsen
2003-10-22 17:01 ` Ben Greear
2003-11-12 19:48 ` Rask Ingemann Lambertsen [this message]
2003-07-09 17:15 ` Ben Greear
2003-07-09 19:12 ` Andrius Kasparavicius
2003-07-11 14:59 ` Andrius Kasparavicius
2003-07-11 17:11 ` Ben Greear
2003-07-11 17:18 ` Jeff Garzik
2003-07-11 17:25 ` Ben Greear
-- strict thread matches above, loose matches on Subject: below --
2003-07-09 15:33 Hen, Shmulik
2003-07-09 17:13 ` 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=20031112204804.B968@sygehus.dk \
--to=rask@sygehus.dk \
--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).