I fully agree with Steve. The netgraph code is ideal to handle the vlan
stuff. Take a look at the port aggregation (etherchannel) Bill Paul has done
as well
-----Original Message-----
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Vladimir B.
Grebenschikov
Sent: Sunday, July 22, 2001 12:26
To: C. Stephen Gunn
Cc: Brooks Davis; [EMAIL PROTECTED]
Subject: Re: sysctl net.link.vlan.link.proto
C. Stephen Gunn writes:
> > I'm working on modernizing the vlan device (making it loadable,
> > unloadable, and clonable) and I've run into this sysctl.
>
> This shoud allow you to move the check for 802.1q packets down into
> the normal ether_demux() which classifies packets based on ethertype.
>
> The former code was a check right above the main switch statement in
> ether_demux() because it was a sysctl, not a constant.
>
> I have some other patches around that ease the interrupt-time
requirements
> by scheduling a NETISR for vlan traffic. I wasn't ever sure if that was
> a true win, so I didn't contrib them. I could dig them up if you're
> really interested in spiffing up the VLAN code. ;-)
May be most right way to handle VLANs is netgraph mechanism ?
I've dig a bit into code and found that to get such mechanism working
it need to add ng_iface node hook to inject not demuxed frames. And
fix a bit code related to ARP.
> - Steve
--
TSB Russian Express, Moscow
Vladimir B. Grebenschikov, [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-net" in the body of the message
