netdev - Re: [PATCH v2 2/2] openvswitch: use percpu flow 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] [day] [month] [year] [list]

Message-Id: <20160918.221422.792448980235933369.davem@davemloft.net>
Date:   Sun, 18 Sep 2016 22:14:22 -0400 (EDT)
From:   David Miller <davem@...emloft.net>
To:     cascardo@...hat.com
Cc:     netdev@...r.kernel.org, dev@...nvswitch.org, pshelar@....org,
        eric.dumazet@...il.com
Subject: Re: [PATCH v2 2/2] openvswitch: use percpu flow stats

From: Thadeu Lima de Souza Cascardo <cascardo@...hat.com>
Date: Thu, 15 Sep 2016 19:11:53 -0300

> Instead of using flow stats per NUMA node, use it per CPU. When using
> megaflows, the stats lock can be a bottleneck in scalability.
> 
> On a E5-2690 12-core system, usual throughput went from ~4Mpps to
> ~15Mpps when forwarding between two 40GbE ports with a single flow
> configured on the datapath.
> 
> This has been tested on a system with possible CPUs 0-7,16-23. After
> module removal, there were no corruption on the slab cache.
> 
> Signed-off-by: Thadeu Lima de Souza Cascardo <cascardo@...hat.com>

Also applied to net-next, thanks.