From: "Varghese, Vipin" <vipin.varghese@intel.com>
To: "Varghese, Vipin" <vipin.varghese@intel.com>,
"Hu, Jiayu" <jiayu.hu@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stephen@networkplumber.org" <stephen@networkplumber.org>,
"Ananyev, Konstantin" <konstantin.ananyev@intel.com>,
"mb@smartsharesystems.com" <mb@smartsharesystems.com>,
"Hu, Jiayu" <jiayu.hu@intel.com>,
"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH V4] doc: add GRO API limitations in prog_guide
Date: Wed, 9 Jan 2019 04:27:14 +0000 [thread overview]
Message-ID: <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D2EBDB2@BGSMSX101.gar.corp.intel.com> (raw)
In-Reply-To: <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D2EBD96@BGSMSX101.gar.corp.intel.com>
Typo in previous email
why there is document update patch with no code update patch shared?
> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of Varghese, Vipin
> Sent: Wednesday, January 9, 2019 9:55 AM
> To: Hu, Jiayu <jiayu.hu@intel.com>; dev@dpdk.org
> Cc: stephen@networkplumber.org; Ananyev, Konstantin
> <konstantin.ananyev@intel.com>; mb@smartsharesystems.com; Hu, Jiayu
> <jiayu.hu@intel.com>; stable@dpdk.org
> Subject: Re: [dpdk-dev] [PATCH V4] doc: add GRO API limitations in prog_guide
>
> Hi Jiayu Hu,
>
> A request to information, why there is document update patch with code
> update patch shared?
>
> 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?
>
> Thanks
> Vipin Varghese
>
> > -----Original Message-----
> > From: dev <dev-bounces@dpdk.org> On Behalf Of Jiayu Hu
> > Sent: Wednesday, January 9, 2019 8:30 AM
> > To: dev@dpdk.org
> > Cc: stephen@networkplumber.org; Ananyev, Konstantin
> > <konstantin.ananyev@intel.com>; mb@smartsharesystems.com; Hu, Jiayu
> > <jiayu.hu@intel.com>; 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 <jiayu.hu@intel.com>
> > ---
> > 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
next prev parent reply other threads:[~2019-01-09 4:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-18 4:25 [dpdk-dev] [PATCH] doc: add GRO API requirement " Jiayu Hu
2018-12-26 4:04 ` [dpdk-dev] [PATCH v2] doc: add GRO API limitations " Jiayu Hu
2019-01-04 7:16 ` [dpdk-dev] [PATCH v3] " Jiayu Hu
2019-01-09 3:00 ` [dpdk-dev] [PATCH V4] " Jiayu Hu
2019-01-09 4:25 ` Varghese, Vipin
2019-01-09 4:27 ` Varghese, Vipin [this message]
2019-01-09 5:18 ` Hu, Jiayu
2019-01-09 8:19 ` [dpdk-dev] [PATCH v5] " Jiayu Hu
2019-01-09 18:20 ` Stephen Hemminger
2019-01-09 18:40 ` Ananyev, Konstantin
2019-01-09 21:31 ` Morten Brørup
2019-01-10 8:06 ` Hu, Jiayu
2019-01-10 8:28 ` Morten Brørup
2019-01-16 2:13 ` [dpdk-dev] [PATCH v6] doc: add GRO " Jiayu Hu
2019-01-16 9:50 ` Ananyev, Konstantin
2019-01-17 22:08 ` Thomas Monjalon
2019-01-17 13:55 ` Kovacevic, Marko
2019-01-17 22:08 ` [dpdk-dev] [dpdk-stable] " Thomas Monjalon
2019-01-04 19:35 ` [dpdk-dev] [PATCH] doc: add GRO API requirement " Stephen Hemminger
2019-01-08 2:35 ` Hu, Jiayu
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=4C9E0AB70F954A408CC4ADDBF0F8FA7D4D2EBDB2@BGSMSX101.gar.corp.intel.com \
--to=vipin.varghese@intel.com \
--cc=dev@dpdk.org \
--cc=jiayu.hu@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=mb@smartsharesystems.com \
--cc=stable@dpdk.org \
--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).