Date: Fri, 31 Aug 2007 09:21:54 -0700 From: "Jack Vogel" <jfvogel@gmail.com> To: "Tom Judge" <tom@tomjudge.com> Cc: "freebsd-net@freebsd.org" <freebsd-net@freebsd.org>, Andre Oppermann <andre@freebsd.org>, John Baldwin <jhb@yahoo-inc.com> Subject: Re: vlan filtering Message-ID: <2a41acea0708310921ic12931bt86e76f3e9fbf5556@mail.gmail.com> In-Reply-To: <46D7E4B8.4030609@tomjudge.com> References: <2a41acea0708301622j6b4eeab9h62576dcfd1325b0a@mail.gmail.com> <46D7E4B8.4030609@tomjudge.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On 8/31/07, Tom Judge <tom@tomjudge.com> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?2a41acea0708310921ic12931bt86e76f3e9fbf5556>