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 V3 0/2] gro: add UDP GRO and VXLAN UDP GRO support
Date: Wed, 2 Sep 2020 17:26:41 +0800 [thread overview]
Message-ID: <20200902092643.49924-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.
Changelog
---------
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/Makefile | 2 +
lib/librte_gro/gro_udp4.c | 435 +++++++++++++++++++++++++++++++
lib/librte_gro/gro_udp4.h | 294 +++++++++++++++++++++
lib/librte_gro/gro_vxlan_udp4.c | 556 ++++++++++++++++++++++++++++++++++++++++
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 +-
8 files changed, 1607 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-02 9:26 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-02 9:26 yang_y_yi [this message]
2020-09-02 9:26 ` [dpdk-dev] [PATCH V3 1/2] gro: add " yang_y_yi
2020-09-03 7:42 ` Hu, Jiayu
2020-09-04 1:26 ` yang_y_yi
2020-09-02 9:26 ` [dpdk-dev] [PATCH V3 2/2] gro: add VXLAN " 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=20200902092643.49924-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).