From: yang_y_yi@163.com
To: dev@dpdk.org
Cc: jiayu.hu@intel.com, thomas@monjalon.net, yangyi01@inspur.com,
yang_y_yi@163.com
Subject: [dpdk-dev] [PATCH v5 0/2] gro: add UDP GRO and VXLAN UDP GRO support
Date: Thu, 10 Sep 2020 17:29:12 +0800 [thread overview]
Message-ID: <20200910092914.120452-1-yang_y_yi@163.com> (raw)
From: Yi Yang <yangyi01@inspur.com>
In case that UFO or GSO is enabled, GRO is very necessary,
especially for UDP, it is more so. Many NICs can't support
VXLAN UDP UFO/USO and VLAN UFO/USO, so UDP performance
improvement depends on GSO and GRO to a great extent.
This patch series added VLAN UDP GRO and VXLAN UDP GRO
support.
I have tested it in OVS DPDK, test scenario is as below:
+-------------------------+ +--------------------------+
|VM1 --- OVS DPDK --- NIC1|---| NIC2 --- OVS-DPDK --- VM2|
+-------------------------+ +--------------------------+
SERVER1 SERVER2
If no GSO and GRO, 8k UDP packet can't work in case of UFO or
in case that underlay MTU is 1500, so UDP size must meet MTU
limitation, my VM MTU is 1450 (consider vxlan header), UDP
performance is about 3Gbps, with GSO and GRO enabled, I can
send 8K UDP packet, UDP performance is about 6Gbps (Note: with
small UDP packet loss rate).
FYI: OVS DPDK patch series
https://patchwork.ozlabs.org/project/openvswitch/list/?series=194621
Changelog
---------
v4 -> v5: remove duplicate line
fix header length check issue
add unlikely for some low probability condition branch
rename udp_check_neighbor to udp4_check_neighbor
remove brace for single line else statement
remove outer_l2_len and pkt->outer_l3_len because they
are nonsense for non-VXLAN UDP packet
v3 -> v4: split two patches in cleaner way
remove ip_id which is unnecessary for UDP GRO
correct hdr_len calculation
v2 -> v3: remove UDP header length check
v1 -> v2: split into two patches
Yi Yang (2):
gro: add UDP GRO support
gro: add VXLAN UDP GRO support
lib/librte_gro/gro_udp4.c | 430 +++++++++++++++++++++++++++++++
lib/librte_gro/gro_udp4.h | 282 +++++++++++++++++++++
lib/librte_gro/gro_vxlan_udp4.c | 548 ++++++++++++++++++++++++++++++++++++++++
lib/librte_gro/gro_vxlan_udp4.h | 152 +++++++++++
lib/librte_gro/meson.build | 2 +-
lib/librte_gro/rte_gro.c | 192 +++++++++++---
lib/librte_gro/rte_gro.h | 8 +-
7 files changed, 1580 insertions(+), 34 deletions(-)
create mode 100644 lib/librte_gro/gro_udp4.c
create mode 100644 lib/librte_gro/gro_udp4.h
create mode 100644 lib/librte_gro/gro_vxlan_udp4.c
create mode 100644 lib/librte_gro/gro_vxlan_udp4.h
--
1.8.3.1
next reply other threads:[~2020-09-10 9:29 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-10 9:29 yang_y_yi [this message]
2020-09-10 9:29 ` [dpdk-dev] [PATCH v5 1/2] gro: add " yang_y_yi
2020-09-10 9:29 ` [dpdk-dev] [PATCH v5 2/2] gro: add VXLAN " yang_y_yi
[not found] ` <20200911042416.GA46174@NPG_DPDK_VIRTIO_jiayuhu_15.sh.intel.com>
[not found] ` <1623572b.1b82.1748a63b63f.Coremail.yang_y_yi@163.com>
2020-09-14 4:21 ` Jiayu Hu
2020-09-14 7:11 ` yang_y_yi
2020-09-14 8:26 ` yang_y_yi
2020-09-14 8:50 ` Hu, Jiayu
2020-09-14 9:14 ` yang_y_yi
2020-09-16 2:54 ` Jiayu Hu
2020-09-16 3:05 ` yang_y_yi
2020-09-16 4:19 ` Stephen Hemminger
2020-09-17 2:06 ` Hu, Jiayu
2020-09-17 2:21 ` yang_y_yi
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=20200910092914.120452-1-yang_y_yi@163.com \
--to=yang_y_yi@163.com \
--cc=dev@dpdk.org \
--cc=jiayu.hu@intel.com \
--cc=thomas@monjalon.net \
--cc=yangyi01@inspur.com \
/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;
as well as URLs for NNTP newsgroup(s).