| lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
|
Open Source and information security mailing list archives
| ||
|
Message-ID: <AANLkTinD7fTvX4yfVWJs4oxx6fYA0m5snct6d+qFUg8D@mail.gmail.com> Date: Mon, 22 Nov 2010 18:02:04 -0800 From: Jesse Gross <jesse@...ira.com> To: Roger Luethi <rl@...lgate.ch> Cc: netdev@...r.kernel.org, "David S. Miller" <davem@...emloft.net> Subject: Re: [PATCH] via-rhine: hardware VLAN support On Sun, Nov 21, 2010 at 5:17 AM, Roger Luethi <rl@...lgate.ch> wrote: > On Mon, 08 Nov 2010 12:53:57 -0800, Jesse Gross wrote: >> On Mon, Nov 8, 2010 at 8:21 AM, Roger Luethi <rl@...lgate.ch> wrote: >> > On Fri, 05 Nov 2010 11:31:56 -0700, Jesse Gross wrote: >> > Can you point me to a driver that has been switched to use the new methods >> > already? Is there some other form of documentation? >> >> bnx2 is an example of a driver that has been converted. The commit >> that actually made the change was >> 7d0fd2117e3d0550d7987b3aff2bfbc0244cf7c6, which should highlight the >> differences. A key point is that drivers should no longer reference >> vlan groups at all. > > bnx2 does not support hardware VLAN filters, but ixgbe does (converted by > commit f62bbb5e62c6e4a91fb222d22bc46e8d4d7e59ef). ixgbe keeps a list of > configured VLANs in a device private data structure (active_vlans). Is that > the model to follow? Yes, that's right. The driver should store whatever information it requires to manage the CAM or restore the state after a board reset. -- To unsubscribe from this list: send the line "unsubscribe netdev" in the body of a message to majordomo@...r.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists