Netdev List
 help / color / mirror / Atom feed
From: xiangxia.m.yue@gmail.com
To: pshelar@ovn.org, gvrose8192@gmail.com
Cc: netdev@vger.kernel.org, Tonghao Zhang <xiangxia.m.yue@gmail.com>
Subject: [PATCH net-next 0/7] optimize openvswitch flow looking up
Date: Fri, 20 Sep 2019 00:54:46 +0800	[thread overview]
Message-ID: <1568912093-68535-1-git-send-email-xiangxia.m.yue@gmail.com> (raw)

From: Tonghao Zhang <xiangxia.m.yue@gmail.com>

This series patch optimize openvswitch.

Patch 1, 2, 4: Port Pravin B Shelar patches to
linux upstream with little changes.

Patch 5, 6, 7: Optimize the flow looking up and
simplify the flow hash.

The performance test is on Intel Xeon E5-2630 v4.
The test topology is show as below:

+-----------------------------------+
|   +---------------------------+   |
|   | eth0   ovs-switch    eth1 |   | Host0
|   +---------------------------+   |
+-----------------------------------+
      ^                       |
      |                       |
      |                       |
      |                       |
      |                       v
+-----+----+             +----+-----+
| netperf  | Host1       | netserver| Host2
+----------+             +----------+

We use netperf send the 64B frame, and insert 255+ flow-mask:
$ ovs-dpctl add-flow ovs-switch "in_port(1),eth(dst=00:01:00:00:00:00/ff:ff:ff:ff:ff:01),eth_type(0x0800),ipv4(frag=no)" 2
...
$ ovs-dpctl add-flow ovs-switch "in_port(1),eth(dst=00:ff:00:00:00:00/ff:ff:ff:ff:ff:ff),eth_type(0x0800),ipv4(frag=no)" 2
$ netperf -t UDP_STREAM -H 2.2.2.200 -l 40 -- -m 18

* Without series patch, throughput 8.28Mbps
* With series patch, throughput 46.05Mbps

Tonghao Zhang (7):
  net: openvswitch: add flow-mask cache for performance
  net: openvswitch: convert mask list in mask array
  net: openvswitch: shrink the mask array if necessary
  net: openvswitch: optimize flow mask cache hash collision
  net: openvswitch: optimize flow-mask looking up
  net: openvswitch: simplify the flow_hash
  net: openvswitch: add likely in flow_lookup

 net/openvswitch/datapath.c   |   3 +-
 net/openvswitch/flow.h       |   1 -
 net/openvswitch/flow_table.c | 308 ++++++++++++++++++++++++++++++++++++-------
 net/openvswitch/flow_table.h |  19 ++-
 4 files changed, 282 insertions(+), 49 deletions(-)

-- 
1.8.3.1


             reply	other threads:[~2019-09-26  8:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-19 16:54 xiangxia.m.yue [this message]
2019-09-19 16:54 ` [PATCH net-next 1/7] net: openvswitch: add flow-mask cache for performance xiangxia.m.yue
2019-09-19 16:54 ` [PATCH net-next 2/7] net: openvswitch: convert mask list in mask array xiangxia.m.yue
2019-09-19 16:54 ` [PATCH net-next 3/7] net: openvswitch: shrink the mask array if necessary xiangxia.m.yue
2019-09-19 16:54 ` [PATCH net-next 4/7] net: openvswitch: optimize flow mask cache hash collision xiangxia.m.yue
2019-09-19 16:54 ` [PATCH net-next 5/7] net: openvswitch: optimize flow-mask looking up xiangxia.m.yue
2019-09-19 16:54 ` [PATCH net-next 6/7] net: openvswitch: simplify the flow_hash xiangxia.m.yue
2019-09-19 16:54 ` [PATCH net-next 7/7] net: openvswitch: add likely in flow_lookup xiangxia.m.yue
2019-09-26 10:14 ` [PATCH net-next 0/7] optimize openvswitch flow looking up David Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1568912093-68535-1-git-send-email-xiangxia.m.yue@gmail.com \
    --to=xiangxia.m.yue@gmail.com \
    --cc=gvrose8192@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=pshelar@ovn.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox