DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jiayu Hu <jiayu.hu@intel.com>
To: dev@dpdk.org
Cc: bruce.richardson@intel.com, junjie.j.chen@intel.com,
	jianfeng.tan@intel.com, stephen@networkplumber.org,
	ferruh.yigit@intel.com, konstantin.ananyev@intel.com,
	lei.a.yao@intel.com, Jiayu Hu <jiayu.hu@intel.com>
Subject: [dpdk-dev] [PATCH v4 0/2] Support VxLAN GRO
Date: Fri,  5 Jan 2018 14:12:47 +0800	[thread overview]
Message-ID: <1515132769-52572-1-git-send-email-jiayu.hu@intel.com> (raw)
In-Reply-To: <1513927544-97241-1-git-send-email-jiayu.hu@intel.com>

VxLAN is one of the most widely used tunneled protocols. Providing GRO
support for VxLAN-encapsulated packets can benefit many per-packet based
applications, like Open vSwitch.

This patchset is to support VxLAN GRO. The first patch cleans up current
gro codes for the sake of supporting tunneled GRO. The second patch
supports GRO on the VxLAN packets which have an outer IPv4 header and an
inner TCP/IPv4 packet.

Change log
===========
v4:
- replace gro-key-algorithm.png with gro-key-algorithm.svg
- reduce key comparison times in gro_tcp4_reassemble() and
  gro_vxlan_tcp4_reassemble()
- reduce comparison times in rte_gro_get_pkt_count()
v3:
- remove needless check
- add "likely()" and "unlikely()" to optimize branch prediction
- fix a bug in merge_two_tcp4_packets(): for VxLAN packets, check if
  the outer IPv4 packet length is less than or equal to UINT16_MAX,
  rather than the inner IPv4 packet length.
- fix a bug in rte_gro.h: change RTE_GRO_TYPE_SUPPORT_NUM to 2
- Avoid inserting timestamp in rte_gro_reassemble_burst(), since all
  packets in the tables will be flushed.
- fix typos
v2:
- comply RFC 6848 to process IP ID fields. Specifically, we require the
  IP ID fields of neighbor packets whose DF bit is 0 to be increased by
  1. We don't check IP ID for the packets whose DF bit is 1.
  Additionally, packets whose DF bits are different cannot be merged.
- update the programmer guide and function comments

Jiayu Hu (2):
  gro: code cleanup
  gro: support VxLAN GRO

 .../prog_guide/generic_receive_offload_lib.rst     | 269 +++++++----
 doc/guides/prog_guide/img/gro-key-algorithm.svg    | 223 +++++++++
 lib/librte_gro/Makefile                            |   1 +
 lib/librte_gro/gro_tcp4.c                          | 339 +++++---------
 lib/librte_gro/gro_tcp4.h                          | 253 +++++++---
 lib/librte_gro/gro_vxlan_tcp4.c                    | 521 +++++++++++++++++++++
 lib/librte_gro/gro_vxlan_tcp4.h                    | 184 ++++++++
 lib/librte_gro/rte_gro.c                           | 203 +++++---
 lib/librte_gro/rte_gro.h                           |  97 ++--
 9 files changed, 1575 insertions(+), 515 deletions(-)
 create mode 100644 doc/guides/prog_guide/img/gro-key-algorithm.svg
 create mode 100644 lib/librte_gro/gro_vxlan_tcp4.c
 create mode 100644 lib/librte_gro/gro_vxlan_tcp4.h

-- 
2.7.4

  parent reply	other threads:[~2018-01-05  6:08 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-25  3:17 [dpdk-dev] [PATCH " Jiayu Hu
2017-11-25  3:17 ` [dpdk-dev] [PATCH 1/2] gro: TCP/IPV4 GRO codes cleanup Jiayu Hu
2017-11-25  3:17 ` [dpdk-dev] [PATCH 2/2] gro: support VxLAN GRO Jiayu Hu
2017-12-14  2:49 ` [dpdk-dev] [PATCH v2 0/2] Support " Jiayu Hu
2017-12-14  2:49   ` [dpdk-dev] [PATCH v2 1/2] gro: code cleanup Jiayu Hu
2017-12-14  2:49   ` [dpdk-dev] [PATCH v2 2/2] gro: support VxLAN GRO Jiayu Hu
2017-12-14  2:58     ` Stephen Hemminger
2017-12-14  3:02     ` Stephen Hemminger
2017-12-14  4:37       ` Hu, Jiayu
2017-12-22  7:25   ` [dpdk-dev] [PATCH v3 0/2] Support " Jiayu Hu
2017-12-22  7:25     ` [dpdk-dev] [PATCH v3 1/2] gro: code cleanup Jiayu Hu
2017-12-29  3:53       ` Chen, Junjie J
2018-01-02 11:26       ` Bruce Richardson
2018-01-03  1:07         ` Tan, Jianfeng
2018-01-03  1:27           ` Stephen Hemminger
2017-12-22  7:25     ` [dpdk-dev] [PATCH v3 2/2] gro: support VxLAN GRO Jiayu Hu
2017-12-22  8:17       ` Chen, Junjie J
2017-12-25  6:36         ` Jiayu Hu
2017-12-29  3:53       ` Chen, Junjie J
2017-12-29  3:52     ` [dpdk-dev] [PATCH v3 0/2] Support " Chen, Junjie J
2018-01-05  6:12     ` Jiayu Hu [this message]
2018-01-05  6:12       ` [dpdk-dev] [PATCH v4 1/2] gro: code cleanup Jiayu Hu
2018-01-08  1:15         ` Yao, Lei A
2018-01-10  0:09         ` Thomas Monjalon
2018-01-10  1:55           ` Hu, Jiayu
2018-01-05  6:12       ` [dpdk-dev] [PATCH v4 2/2] gro: support VxLAN GRO Jiayu Hu
2018-01-10 14:03       ` [dpdk-dev] [PATCH v5 0/3] Support " Jiayu Hu
2018-01-10 14:03         ` [dpdk-dev] [PATCH v5 1/3] gro: codes cleanup Jiayu Hu
2018-01-10 14:03         ` [dpdk-dev] [PATCH v5 2/3] gro: comply RFC 6864 to process IPv4 ID Jiayu Hu
2018-01-10 14:03         ` [dpdk-dev] [PATCH v5 3/3] gro: support VxLAN GRO Jiayu Hu
2018-01-11 22:15         ` [dpdk-dev] [PATCH v5 0/3] Support " Thomas Monjalon

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=1515132769-52572-1-git-send-email-jiayu.hu@intel.com \
    --to=jiayu.hu@intel.com \
    --cc=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jianfeng.tan@intel.com \
    --cc=junjie.j.chen@intel.com \
    --cc=konstantin.ananyev@intel.com \
    --cc=lei.a.yao@intel.com \
    --cc=stephen@networkplumber.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;
as well as URLs for NNTP newsgroup(s).