netdev - Re: [PATCH net-next v2 0/5] bridge: per-vlan stats

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20160429.161208.1214717753456694357.davem@davemloft.net>
Date:	Fri, 29 Apr 2016 16:12:08 -0400 (EDT)
From:	David Miller <davem@...emloft.net>
To:	nikolay@...ulusnetworks.com
Cc:	netdev@...r.kernel.org, roopa@...ulusnetworks.com,
	stephen@...workplumber.org, jhs@...atatu.com
Subject: Re: [PATCH net-next v2 0/5] bridge: per-vlan stats

From: Nikolay Aleksandrov <nikolay@...ulusnetworks.com>
Date: Fri, 29 Apr 2016 21:49:17 +0200

> Because that is not needed for the per-vlan stats to work, I did to
> unify the paths and simplify the pvid code but I can easily drop it
> and revert back to using the direct pvid id.  The only fetch will be
> the stats per-cpu pointer then. Would that be acceptable ?

It would be a step in the right direction, for sure.