Re: vlan filtering
- From: "Jack Vogel" <jfvogel@xxxxxxxxx>
- Date: Fri, 31 Aug 2007 09:21:54 -0700
On 8/31/07, Tom Judge <tom@xxxxxxxxxxxx> wrote:
Jack Vogel wrote:
I was just working on a bug in the Oplin driver that had me look
a bit more at VLAN code than I had previously.
FreeBSD has apparently never used the hardware vlan filtering
that our hardware can do, is there a systemic reason for this,
or has the code lagged in its use of the system?
I at least don't understand how the driver is supposed to get
the vlan id to set in the filter, am I just unenlightened? :)
If this is doable I can add code into em as well as ixgbe.
Jack
This isn't really directly related but could be important for some
users. If you where to use this would the card handle Q in Q properly
with the filter on or would there have to be some form of administrative
option to turn the hardware filter on/off?
I like flexibility, so having it be a feature that could be enabled or not
seems like a good idea to me. Once I understand the situation we'll
see.
Cheers,
Jack
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"
- References:
- vlan filtering
- From: Jack Vogel
- Re: vlan filtering
- From: Tom Judge
- vlan filtering
- Prev by Date: Re: pf rdr + netsed : reinject loop...
- Next by Date: Re: Odd congestion window behaviour [ was: Draft email to freebsd-net ]
- Previous by thread: Re: vlan filtering
- Next by thread: Accessing device memory from user-land application process
- Index(es):
Relevant Pages
|
|
