Thread (10 messages) 10 messages, 2 authors, 2013-12-05

Re: [net-next 3/7] openvswitch: Enable memory mapped Netlink i/o

From: Jesse Gross <hidden>
Date: 2013-12-04 05:45:27

On Sat, Nov 30, 2013 at 4:21 AM, Thomas Graf [off-list ref] wrote:
Use memory mapped Netlink i/o for all unicast openvswitch
communication if a ring has been set up.

Benchmark
  * pktgen -> ovs internal port
  * 5M pkts, 5M flows
  * 4 threads, 8 cores

Before:
Result: OK: 67418743(c67108212+d310530) usec, 5000000 (9000byte,0frags)
  74163pps 5339Mb/sec (5339736000bps) errors: 0
        +   2.98%     ovs-vswitchd  [k] copy_user_generic_string
        +   2.49%     ovs-vswitchd  [k] memcpy
        +   1.84%       kpktgend_2  [k] memcpy
        +   1.81%       kpktgend_1  [k] memcpy
        +   1.81%       kpktgend_3  [k] memcpy
        +   1.78%       kpktgend_0  [k] memcpy

After:
Result: OK: 24229690(c24127165+d102524) usec, 5000000 (9000byte,0frags)
  206358pps 14857Mb/sec (14857776000bps) errors: 0
        +   2.80%     ovs-vswitchd  [k] memcpy
        +   1.31%       kpktgend_2  [k] memcpy
        +   1.23%       kpktgend_0  [k] memcpy
        +   1.09%       kpktgend_1  [k] memcpy
        +   1.04%       kpktgend_3  [k] memcpy
        +   0.96%     ovs-vswitchd  [k] copy_user_generic_string

Signed-off-by: Thomas Graf <tgraf@suug.ch>
Reviewed-by: Daniel Borkmann <redacted>
First three patches applied, thanks.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help