From: Ben Greear <greearb@candelatech.com>
To: "David S. Miller" <davem@redhat.com>
Cc: netdev@oss.sgi.com
Subject: Re: MAC-VLANS
Date: Tue, 05 Aug 2003 21:10:47 -0700 [thread overview]
Message-ID: <3F307FC7.10908@candelatech.com> (raw)
In-Reply-To: <20030805204028.644895dc.davem@redhat.com>
David S. Miller wrote:
> On Tue, 05 Aug 2003 17:33:03 -0700
> Ben Greear <greearb@candelatech.com> 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@candelatech.com>
Candela Technologies Inc http://www.candelatech.com
prev parent reply other threads:[~2003-08-06 4:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-06 0:33 MAC-VLANS Ben Greear
2003-08-06 3:40 ` MAC-VLANS David S. Miller
2003-08-06 4:10 ` Ben Greear [this message]
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=3F307FC7.10908@candelatech.com \
--to=greearb@candelatech.com \
--cc=davem@redhat.com \
--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).