| To: | netdev@xxxxxxxxxxx |
|---|---|
| Subject: | Re: network interface cards native vlans support in linux kernel? |
| From: | Rask Ingemann Lambertsen <rask@xxxxxxxxxx> |
| Date: | Wed, 12 Nov 2003 20:48:04 +0100 |
| In-reply-to: | <3F96B7FD.7080607@candelatech.com>; from greearb@candelatech.com on Wed, Oct 22, 2003 at 10:01:49AM -0700 |
| References: | <Pine.LNX.4.44.0307091816280.1313-100000@hl.kauneta.net> <20030709152814.GC15293@gtf.org> <20031022140624.A9145@vip.cybercity.dk> <3F96B7FD.7080607@candelatech.com> |
| Sender: | netdev-bounce@xxxxxxxxxxx |
| User-agent: | Mutt/1.2.5.1i |
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 |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | Re: [PATCH] Updated 8139too with NAPI, Jeff Garzik |
|---|---|
| Next by Date: | Re: [PATCH] ethertap can use alloc_etherdev, Jeff Garzik |
| Previous by Thread: | tracing a packet through the kernel stack, francois donzet |
| Next by Thread: | [PATCH] de4x5 - missing free on error path, Stephen Hemminger |
| Indexes: | [Date] [Thread] [Top] [All Lists] |