From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga09.intel.com (mga09.intel.com [134.134.136.24]) by dpdk.org (Postfix) with ESMTP id 8AEC21B1F0; Wed, 9 Jan 2019 05:27:31 +0100 (CET) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga006.jf.intel.com ([10.7.209.51]) by orsmga102.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 08 Jan 2019 20:27:30 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.56,455,1539673200"; d="scan'208";a="106773530" Received: from fmsmsx106.amr.corp.intel.com ([10.18.124.204]) by orsmga006.jf.intel.com with ESMTP; 08 Jan 2019 20:27:30 -0800 Received: from bgsmsx109.gar.corp.intel.com (10.223.4.211) by FMSMSX106.amr.corp.intel.com (10.18.124.204) with Microsoft SMTP Server (TLS) id 14.3.408.0; Tue, 8 Jan 2019 20:27:30 -0800 Received: from bgsmsx101.gar.corp.intel.com ([169.254.1.128]) by BGSMSX109.gar.corp.intel.com ([169.254.10.162]) with mapi id 14.03.0415.000; Wed, 9 Jan 2019 09:57:14 +0530 From: "Varghese, Vipin" To: "Varghese, Vipin" , "Hu, Jiayu" , "dev@dpdk.org" CC: "stephen@networkplumber.org" , "Ananyev, Konstantin" , "mb@smartsharesystems.com" , "Hu, Jiayu" , "stable@dpdk.org" Thread-Topic: [dpdk-dev] [PATCH V4] doc: add GRO API limitations in prog_guide Thread-Index: AQHUp8eJ6czCTD7ksUStfAyvKMOVOKWmVqRwgAAA6IA= Date: Wed, 9 Jan 2019 04:27:14 +0000 Message-ID: <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D2EBDB2@BGSMSX101.gar.corp.intel.com> References: <1546586200-38148-1-git-send-email-jiayu.hu@intel.com> <1547002811-6989-1-git-send-email-jiayu.hu@intel.com> <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D2EBD96@BGSMSX101.gar.corp.intel.com> In-Reply-To: <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D2EBD96@BGSMSX101.gar.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-ctpclassification: CTP_NT x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiZWE3OTM4YzEtYmFhMy00MjcwLWE3OTItZTJjMzlmOTU1OGVjIiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX05UIn1dfV19LCJTdWJqZWN0TGFiZWxzIjpbXSwiVE1DVmVyc2lvbiI6IjE3LjEwLjE4MDQuNDkiLCJUcnVzdGVkTGFiZWxIYXNoIjoiV1Q2ZW1xbVR2TWZmcDQyVEJwajZtQ1VuWGhyWkNjU1RCbktuYXludUlTWSs2ZElSN1wvMmdiaDJPZnRmQjBBS1cifQ== dlp-product: dlpe-windows dlp-version: 11.0.400.15 dlp-reaction: no-action x-originating-ip: [10.223.10.10] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Subject: Re: [dpdk-dev] [PATCH V4] doc: add GRO API limitations in prog_guide X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Jan 2019 04:27:32 -0000 Typo in previous email why there is document update patch with no code update patch shared? > -----Original Message----- > From: dev On Behalf Of Varghese, Vipin > Sent: Wednesday, January 9, 2019 9:55 AM > To: Hu, Jiayu ; dev@dpdk.org > Cc: stephen@networkplumber.org; Ananyev, Konstantin > ; mb@smartsharesystems.com; Hu, Jiayu > ; stable@dpdk.org > Subject: Re: [dpdk-dev] [PATCH V4] doc: add GRO API limitations in prog_g= uide >=20 > Hi Jiayu Hu, >=20 > A request to information, why there is document update patch with code > update patch shared? >=20 > As per DPDK 19.02-rc1 both code and document should be one patch. Can you > share the code patch reference if it was applied before 19.02-rc1? >=20 > Thanks > Vipin Varghese >=20 > > -----Original Message----- > > From: dev On Behalf Of Jiayu Hu > > Sent: Wednesday, January 9, 2019 8:30 AM > > To: dev@dpdk.org > > Cc: stephen@networkplumber.org; Ananyev, Konstantin > > ; mb@smartsharesystems.com; Hu, Jiayu > > ; stable@dpdk.org > > Subject: [dpdk-dev] [PATCH V4] doc: add GRO API limitations in > > prog_guide > > > > This patch adds GRO API limitations in the programmer guide. > > > > Fixes: 2c900d09055e ("doc: add GRO guide") > > Fixes: 9e0b9d2ec0f4 ("gro: support VxLAN GRO") > > Cc: stable@dpdk.org > > > > Signed-off-by: Jiayu Hu > > --- > > changes in v4: > > - update MBUF->l2_len/... requirement > > changes in v3: > > - add MBUF limitation > > changes in v2: > > - add fix versions > > - add more limitations > > > > doc/guides/prog_guide/generic_receive_offload_lib.rst | 17 > > +++++++++++++++++ > > 1 file changed, 17 insertions(+) > > > > diff --git a/doc/guides/prog_guide/generic_receive_offload_lib.rst > > b/doc/guides/prog_guide/generic_receive_offload_lib.rst > > index 9c6a4d0..53c9d5c 100644 > > --- a/doc/guides/prog_guide/generic_receive_offload_lib.rst > > +++ b/doc/guides/prog_guide/generic_receive_offload_lib.rst > > @@ -191,3 +191,20 @@ Header fields deciding if packets are neighbors > > include: > > ignore IPv4 ID fields for the packets whose DF bit is 1. > > Additionally, packets which have different value of DF bit can= 't > > be merged. > > + > > +GRO Library Limitations > > +----------------------- > > + > > +- GRO library uses the values of MBUF->l2_len/l3_len/l4_len/ > > + outer_l2_len/outer_l3_len to get protocol headers for the > > + input packet, rather than parsing the packet header. Therefore, > > + before call GRO APIs to merge packets, user applications > > + must set MBUF->l2_len/l3_len/l4_len/outer_l2_len/outer_l3_len > > + to the same values as the protocol headers of the packet. > > + > > +- GRO library doesn't support to process packets with IPv4 Options. > > + > > +- GRO library just supports to process the packet organized > > + in a single MBUF. If the input packet consists of multiple > > + MBUFs (i.e. chained MBUFs), GRO reassembly behaviors are > > + unknown. > > -- > > 2.7.4