[lkml]   [2001]   [Jan]   [7]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
On Sun, Jan 07, 2001 at 01:42:50PM +0000, Alan Cox wrote:
> > + * NOTE: That is no longer true with the addition of VLAN tags. Not
> > + * sure which should go first, but I bet it won't make much
> > + * difference if we are running VLANs. The good news is that
> It makes a lot of difference tha the vlan goes 2nd. Most sane people wont
> have vlans active on a high load interface.

VLAN tag header appears as Layer-3 protocol, which then
causes loop into VLAN reception code and back to generic
Layer-3 receiver.

I just tried to pull data from another machine, which
is on normal port thru VLAN trunking port to receiving
machine, and got fast-ether at wire speed. (As near as
ncftp's 11.11 MB/sec is wirespeed..)

> So fix the algorithm. You want the list sorted at this point, or to generate
> a bitmap of free/used entries and scan the list then scan the map
> Question: How do devices with hardware vlan support fit into your model ?

Hardware VLAN support at several network cards is just
to recognize VLAN tags, and then do the right thing
( = skip 4 bytes ) when doing TCP/UDP checksum.

> Alan

/Matti Aarnio
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 12:52    [W:0.159 / U:0.628 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site