[Top] [All Lists]

Re: [PATCH] hashed device lookup (Does NOT meet Linus' sumission

To: jamal <hadi@xxxxxxxxxx>
Subject: Re: [PATCH] hashed device lookup (Does NOT meet Linus' sumission
From: Ben Greear <greearb@xxxxxxxxxxxxxxx>
Date: Sun, 07 Jan 2001 12:37:30 -0700
Cc: Alan Cox <alan@xxxxxxxxxxxxxxxxxxx>, "David S. Miller" <davem@xxxxxxxxxx>, linux-kernel@xxxxxxxxxxxxxxx, netdev@xxxxxxxxxxx
Organization: Candela Technologies
References: <Pine.GSO.4.30.0101071317440.18916-100000@xxxxxxxxxxxxxxxx>
Sender: owner-netdev@xxxxxxxxxxx
jamal wrote:
> On Sun, 7 Jan 2001, Ben Greear wrote:
> > > Question: How do devices with hardware vlan support fit into your model ?
> >
> > I don't know of any, and I'm not sure how they would be supported.
> >
> erm, this is a MUST. You MUST factor the hardware VLANs and be totaly
> 802.1q compliant. Also of interest is 802.1P and D. We must have full
> compliance, not some toy emulation.

I have seen neither hardware nor spec sheets on how these NICs are doing
VLAN 'support'.  So, I don't know what the best way to support them is.

If it requires driver changes, then the ethernet driver folks will need
to be involved.

There is also a difference between supporting hardware VLAN solutions
and being 100% compliant:  If I can send/receive packets that are
100% compliant from an RTL 8139 NIC, then as far as the world (ie Switch) knows,
I am 100% compliant.

If the specific VLAN hardware features are not supported in some exotic
NIC, then that should just mean slightly less performance, or worst cast,
not supporting that particular NIC.

My vlan code supports setting of Priority bits already (thats' the .1P, right?)

What is the .1D stuff about?

> cheers,
> jamal

Ben Greear (greearb@xxxxxxxxxxxxxxx)
Author of ScryMUD: 4444        (Released under GPL)     

<Prev in Thread] Current Thread [Next in Thread>