Skip site navigation (1)Skip section navigation (2)
Date:      Wed, 11 Jun 2008 16:33:14 +0900
From:      Pyun YongHyeon <pyunyh@gmail.com>
To:        Jack Vogel <jfvogel@gmail.com>
Cc:        "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>, FreeBSD Current <freebsd-current@freebsd.org>, FreeBSD Stable List <freebsd-stable@freebsd.org>
Subject:   Re: Vlan EVENT patch
Message-ID:  <20080611073313.GF3529@cdnetworks.co.kr>
In-Reply-To: <2a41acea0806100951x1142edc6qc872d3810c2bd467@mail.gmail.com>
References:  <2a41acea0806100951x1142edc6qc872d3810c2bd467@mail.gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jun 10, 2008 at 09:51:53AM -0700, Jack Vogel wrote:
 > This is a small patch that Sam came up with for me, it will allow
 > drivers to know
 > when a vlan attaches.
 > 
 > It is transparent to any code that doesn't want to change, but this
 > will allow my
 > drivers to finally utilize the vlan hardware filter (something Linux has had for
 > ever but we lacked).
 > 

Just curious, is there any rule how to use that new capability?
Because drivers will receive events whenever VLAN tags are
added/removed they would know how to act for these events. If
promiscuous mode is on for interface, driver should not filter any
VLAN tagged frames, right?
If users want to disable VLAN hardware filtering feature what is
best way to perform this? Introducing a new flag like
IFCAP_VLAN_HWFILT or add a new sysctl that control this feature?
I guess VIA Rhine III also have VLAN hardware filtering capability
so it would be even better if we have a way to share common part.

 > My test group has done some basic testing of this and it is working great.
 > But we wanted to give any vlan users a chance to see, ask questions, or
 > whatever before its committed.
 > 
 > Jack
-- 
Regards,
Pyun YongHyeon



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20080611073313.GF3529>