DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>,
	"Liu, Lingyu" <lingyu.liu@intel.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	"Xing, Beilei" <beilei.xing@intel.com>,
	"Wu, Jingjing" <jingjing.wu@intel.com>,
	"Guo, Junfeng" <junfeng.guo@intel.com>
Subject: Re: [dpdk-dev] [PATCH v1 4/4] doc: update iavf driver FDIR/RSS for GTPoGRE
Date: Mon, 12 Jul 2021 00:24:23 +0000	[thread overview]
Message-ID: <472dfa931b974ee08682fe4bb11b63b2@intel.com> (raw)
In-Reply-To: <1939803.FOfyW7TgvZ@thomas>



> -----Original Message-----
> From: Thomas Monjalon <thomas@monjalon.net>
> Sent: Friday, July 9, 2021 5:00 PM
> To: Zhang, Qi Z <qi.z.zhang@intel.com>; Liu, Lingyu <lingyu.liu@intel.com>
> Cc: dev@dpdk.org; Xing, Beilei <beilei.xing@intel.com>; Wu, Jingjing
> <jingjing.wu@intel.com>; Guo, Junfeng <junfeng.guo@intel.com>
> Subject: Re: [dpdk-dev] [PATCH v1 4/4] doc: update iavf driver FDIR/RSS for
> GTPoGRE
> 
> 07/07/2021 14:57, Lingyu Liu:
> > Update 21.08 release note for GTPoGRE FDIR and RSS.
> >
> > Signed-off-by: Lingyu Liu <lingyu.liu@intel.com>
> > ---
> >  doc/guides/rel_notes/release_21_08.rst | 2 ++
> >  1 file changed, 2 insertions(+)
> >
> > diff --git a/doc/guides/rel_notes/release_21_08.rst
> b/doc/guides/rel_notes/release_21_08.rst
> > index cd02820e68..df719420b8 100644
> > --- a/doc/guides/rel_notes/release_21_08.rst
> > +++ b/doc/guides/rel_notes/release_21_08.rst
> > @@ -64,6 +64,8 @@ New Features
> >  * **Updated Intel iavf driver.**
> >
> >    * Added Tx QoS VF queue TC mapping.
> > +  * Enable FDIR and RSS for GTPoGRE, support filter based on GTPU
> TEID/QFI,
> > +    outer most L3 or inner most l3/l4.
> 
> Should be in past tense.
> Please update the release notes piece by piece in each patch.

Patch 4/4 are squashed into patch 2/4 and patch 3/4 in next-net-intel.

Thanks
Qi
> 
> 


      reply	other threads:[~2021-07-12  0:24 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-06  7:42 [dpdk-dev] [PATCH v2 0/3] Support outer layer FDIR for GTPoGRE packet Lingyu Liu
2021-07-06  2:40 ` Zhang, Qi Z
2021-07-06 22:10   ` Thomas Monjalon
2021-07-06 23:27     ` Zhang, Qi Z
2021-07-06  7:42 ` [dpdk-dev] [PATCH v2 1/3] net/iavf: add flow pattern for GTPoGRE Lingyu Liu
2021-07-06  7:42 ` [dpdk-dev] [PATCH v2 2/3] net/iavf: add AVF FDIR for GTPoGRE tunnel packet Lingyu Liu
2021-07-06  7:42 ` [dpdk-dev] [PATCH v2 3/3] doc: release note for GTPoGRE FDIR Lingyu Liu
2021-07-07 12:57 ` [dpdk-dev] [PATCH v1 0/4] support AVF RSS and FDIR for GTPoGRE packet Lingyu Liu
2021-07-07  7:25   ` Zhang, Qi Z
2021-07-07 12:57   ` [dpdk-dev] [PATCH v1 1/4] net/iavf: support flow pattern for GTPoGRE Lingyu Liu
2021-07-07 12:57   ` [dpdk-dev] [PATCH v1 2/4] net/iavf: support AVF FDIR for GTPoGRE tunnel packet Lingyu Liu
2021-07-07 12:57   ` [dpdk-dev] [PATCH v1 3/4] net/iavf: support AVF RSS for GTPoGRE packet Lingyu Liu
2021-07-07 12:57   ` [dpdk-dev] [PATCH v1 4/4] doc: update iavf driver FDIR/RSS for GTPoGRE Lingyu Liu
2021-07-09  8:59     ` Thomas Monjalon
2021-07-12  0:24       ` Zhang, Qi Z [this message]

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=472dfa931b974ee08682fe4bb11b63b2@intel.com \
    --to=qi.z.zhang@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=jingjing.wu@intel.com \
    --cc=junfeng.guo@intel.com \
    --cc=lingyu.liu@intel.com \
    --cc=thomas@monjalon.net \
    /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).