netdev
[Top] [All Lists]

Re: MAC-VLANS

To: "David S. Miller" <davem@xxxxxxxxxx>
Subject: Re: MAC-VLANS
From: Ben Greear <greearb@xxxxxxxxxxxxxxx>
Date: Tue, 05 Aug 2003 21:10:47 -0700
Cc: netdev@xxxxxxxxxxx
In-reply-to: <20030805204028.644895dc.davem@redhat.com>
Organization: Candela Technologies
References: <3F304CBF.6050902@candelatech.com> <20030805204028.644895dc.davem@redhat.com>
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5a) Gecko/20030718
David S. Miller wrote:
On Tue, 05 Aug 2003 17:33:03 -0700
Ben Greear <greearb@xxxxxxxxxxxxxxx> wrote:


In order to get MAC-VLANs to work, the only way I can see to make
it happen is to put a hook into dev.c in the:


Why not do it the same we do normal VLAN's?  Ie. directly
in the device driver receive method via something akin to
the vlan_hwaccel_*() routines.

You mean in eth.c or something? I don't want to have to put identical code in all drivers, if that's what you're suggesting. It could be done to common drivers if the feature is used enough to warrant it, but we definately need a fallback case to work with all generic drivers, just as .1q does.

802.1q works because we have an extra shim header in there..but
MAC-vlans have no extra header info.  It would be nice to have
a separate 'protocol' list that was able to consume the pkt: that
would allow this to work w/out additional hacks, and could work for
pktgen rx and even bridging.  Of course, not all could be active
at once, but that is no worse than 'hooks' in that regard.  And,
evil ppl could re-write the IP stack, of course, but that doesn't
bother me as much as some folks :)

Ben

--
Ben Greear <greearb@xxxxxxxxxxxxxxx>
Candela Technologies Inc  http://www.candelatech.com



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