From: yang_y_yi <yang_y_yi@163.com>
To: "Hu, Jiayu" <jiayu.hu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"thomas@monjalon.net" <thomas@monjalon.net>,
"yangyi01@inspur.com" <yangyi01@inspur.com>
Subject: Re: [dpdk-dev] [PATCH v7 3/3] doc: update prog_guide and rel_notes for GRO
Date: Fri, 9 Oct 2020 14:34:50 +0800 (CST) [thread overview]
Message-ID: <2f6a9e67.41ea.1750c11bc69.Coremail.yang_y_yi@163.com> (raw)
In-Reply-To: <23f78a917cba450f80c967e0cfabf314@intel.com>
Thomas, only this one of this series hasn't yet been merged, maybe you missed it, also please help merge it, thanks a lot.
At 2020-09-27 12:56:54, "Hu, Jiayu" <jiayu.hu@intel.com> wrote:
>Acked-by: Jiayu Hu <jiayu.hu@intel.com>
>
>> -----Original Message-----
>> From: yang_y_yi@163.com <yang_y_yi@163.com>
>> Sent: Thursday, September 24, 2020 4:58 PM
>> To: dev@dpdk.org
>> Cc: Hu, Jiayu <jiayu.hu@intel.com>; thomas@monjalon.net;
>> yangyi01@inspur.com; yang_y_yi@163.com
>> Subject: [PATCH v7 3/3] doc: update prog_guide and rel_notes for GRO
>>
>> From: Yi Yang <yangyi01@inspur.com>
>>
>> Release 20.11 added UDP/IPv4 and VXLAN UDP/IPv4 support
>> for GRO, so update prog_guide and rel_notes to reflect
>> these changes.
>>
>> Signed-off-by: Yi Yang <yangyi01@inspur.com>
>> ---
>> doc/guides/prog_guide/generic_receive_offload_lib.rst | 6 +++---
>> doc/guides/rel_notes/release_20_11.rst | 6 ++++++
>> 2 files changed, 9 insertions(+), 3 deletions(-)
>>
>> diff --git a/doc/guides/prog_guide/generic_receive_offload_lib.rst
>> b/doc/guides/prog_guide/generic_receive_offload_lib.rst
>> index 5b3fb91..98a5d29 100644
>> --- a/doc/guides/prog_guide/generic_receive_offload_lib.rst
>> +++ b/doc/guides/prog_guide/generic_receive_offload_lib.rst
>> @@ -30,9 +30,9 @@ assumes the packets are complete (i.e., MF==0 &&
>> frag_off==0), when IP
>> fragmentation is possible (i.e., DF==0). Additionally, it complies RFC
>> 6864 to process the IPv4 ID field.
>>
>> -Currently, the GRO library provides GRO supports for TCP/IPv4 packets and
>> -VxLAN packets which contain an outer IPv4 header and an inner TCP/IPv4
>> -packet.
>> +Currently, the GRO library provides GRO supports for TCP/IPv4 and
>> UDP/IPv4
>> +packets as well as VxLAN packets which contain an outer IPv4 header and
>> an
>> +inner TCP/IPv4 or UDP/IPv4 packet.
>>
>> Two Sets of API
>> ---------------
>> diff --git a/doc/guides/rel_notes/release_20_11.rst
>> b/doc/guides/rel_notes/release_20_11.rst
>> index f377ab8..b7f2b68 100644
>> --- a/doc/guides/rel_notes/release_20_11.rst
>> +++ b/doc/guides/rel_notes/release_20_11.rst
>> @@ -78,6 +78,12 @@ New Features
>> ``--portmask=N``
>> where N represents the hexadecimal bitmask of ports used.
>>
>> +* **Add UDP/IPv4 GRO support for VxLAN and non-VxLAN packets.**
>> +
>> + Add UDP/IPv4 GRO support for VxLAN and non-VxLAN packets. For
>> + VxLAN packets, this adds inner UDP/IPv4 support, for non-VxLAN
>> + packets, this adds UDP/IPv4 support.
>> +
>>
>> Removed Items
>> -------------
>> --
>> 1.8.3.1
next prev parent reply other threads:[~2020-10-09 6:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-24 8:57 [dpdk-dev] [PATCH v7 0/3] gro: add UDP/IPv4 GRO and VXLAN UDP/IPv4 GRO support yang_y_yi
2020-09-24 8:57 ` [dpdk-dev] [PATCH v7 1/3] gro: add " yang_y_yi
2020-09-27 4:56 ` Hu, Jiayu
2020-09-24 8:57 ` [dpdk-dev] [PATCH v7 2/3] gro: add VXLAN " yang_y_yi
2020-09-27 1:49 ` Hu, Jiayu
2020-09-27 3:14 ` yang_y_yi
2020-09-27 5:03 ` Jiayu Hu
2020-09-27 4:56 ` Hu, Jiayu
2020-09-24 8:57 ` [dpdk-dev] [PATCH v7 3/3] doc: update prog_guide and rel_notes for GRO yang_y_yi
2020-09-27 4:56 ` Hu, Jiayu
2020-10-09 6:34 ` yang_y_yi [this message]
2020-10-09 6:48 ` Thomas Monjalon
2020-10-09 7:47 ` yang_y_yi
2020-10-09 8:00 ` Thomas Monjalon
2020-10-09 8:11 ` yang_y_yi
2020-10-09 8:45 ` Thomas Monjalon
2020-10-06 19:53 ` [dpdk-dev] [PATCH v7 0/3] gro: add UDP/IPv4 GRO and VXLAN UDP/IPv4 GRO 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=2f6a9e67.41ea.1750c11bc69.Coremail.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).