DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhao1, Wei" <wei.zhao1@intel.com>
To: "Yigit, Ferruh" <ferruh.yigit@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
	"Xing, Beilei" <beilei.xing@intel.com>,
	"maxime.leroy@6wind.com" <maxime.leroy@6wind.com>
Subject: Re: [dpdk-dev] [dpdk-stable] [PATCH v4 2/3] doc: input set requirement of each pctype for FDIR
Date: Thu, 30 Apr 2020 00:52:08 +0000	[thread overview]
Message-ID: <MWHPR11MB1391B3E3C48DAB22454A3A05B7AA0@MWHPR11MB1391.namprd11.prod.outlook.com> (raw)
In-Reply-To: <a176c623-97f8-a15a-9155-c03da1d56ef2@intel.com>

Hi, 


> -----Original Message-----
> From: Yigit, Ferruh <ferruh.yigit@intel.com>
> Sent: Wednesday, April 29, 2020 6:35 PM
> To: Zhao1, Wei <wei.zhao1@intel.com>; dev@dpdk.org
> Cc: stable@dpdk.org; Xing, Beilei <beilei.xing@intel.com>;
> maxime.leroy@6wind.com
> Subject: Re: [dpdk-stable] [PATCH v4 2/3] doc: input set requirement of each
> pctype for FDIR
> 
> On 4/29/2020 3:03 AM, Wei Zhao wrote:
> > Add input set requirement info to i40e doc.
> >
> > Bugzilla ID: 403
> 
> Should this document update backported to the LTS?
> If so which LTS versions are in the scope, it is better if you can add a fixes tag to
> help us to figure out that.

Maybe we can use this, it is the latest update for i40 doc.
Btw, this is not a bug although it is report in bug list.

Fixes: 3d91e097a352 ("doc: add feature support matrix link in i40e guide ")

> 
> > Signed-off-by: Wei Zhao <wei.zhao1@intel.com>
> > ---
> >  doc/guides/nics/i40e.rst | 7 +++++++
> >  1 file changed, 7 insertions(+)
> >
> > diff --git a/doc/guides/nics/i40e.rst b/doc/guides/nics/i40e.rst index
> > 416b3904e..f085a357c 100644
> > --- a/doc/guides/nics/i40e.rst
> > +++ b/doc/guides/nics/i40e.rst
> > @@ -747,6 +747,13 @@ Use 16 Bytes RX Descriptor Size  As i40e PMD
> > supports both 16 and 32 bytes RX descriptor sizes, and 16 bytes size can
> provide helps to high performance of small packets.
> >  Configuration of ``CONFIG_RTE_LIBRTE_I40E_16BYTE_RX_DESC`` in config
> files can be changed to use 16 bytes size RX descriptors.
> >
> > +input set requirement of each pctype for FDIR
> > +~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> > +
> > +Each PCTYPE can only have one specific FDIR input set at one time.
> > +For example, if creating 2 rte_flow rules with different input set
> > +for one PCTYPE, it is will fail and return the info "Conflict with the first rule's
> input set", which means the current rule's input set is conflict with the first
> rule's. Remove the first rule if want to change the input set of the PCTYPE.
> > +
> >  Example of getting best performance with l3fwd example
> >  ------------------------------------------------------
> >
> >


  reply	other threads:[~2020-04-30  0:52 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-27  7:14 [dpdk-dev] [PATCH 0/3] fix i40e bug for flow filter Wei Zhao
2020-04-27  7:14 ` [dpdk-dev] [PATCH 1/3] net/i40e: remove ARP type check for FDIR filter Wei Zhao
2020-04-28  1:20   ` Xing, Beilei
2020-04-28  5:39     ` Zhao1, Wei
2020-04-27  7:14 ` [dpdk-dev] [PATCH 2/3] doc: input set requirement of each pctype for FDIR Wei Zhao
2020-04-27  7:15 ` [dpdk-dev] [PATCH 3/3] net/i40e: remove teardown when flush FDIR filter Wei Zhao
2020-04-28  1:13   ` Xing, Beilei
2020-04-28  1:18     ` Zhao1, Wei
2020-04-28  5:48 ` [dpdk-dev] [PATCH v2 0/3] fix i40e bug for flow filter Wei Zhao
2020-04-28  5:48   ` [dpdk-dev] [PATCH v2 1/3] net/i40e: fix FDIR issue for ARP packets Wei Zhao
2020-04-28  7:38     ` Xing, Beilei
2020-04-28  7:46       ` Zhao1, Wei
2020-04-28  5:48   ` [dpdk-dev] [PATCH v2 2/3] doc: input set requirement of each pctype for FDIR Wei Zhao
2020-04-28  5:48   ` [dpdk-dev] [PATCH v2 3/3] net/i40e: remove teardown when flush FDIR filter Wei Zhao
2020-04-28  7:16     ` Xing, Beilei
2020-04-28  7:44       ` Zhao1, Wei
2020-04-28  7:39   ` [dpdk-dev] [PATCH v3 0/3] fix i40e bug for flow filter Wei Zhao
2020-04-28  7:39     ` [dpdk-dev] [PATCH v3 1/3] net/i40e: fix FDIR issue for ARP packets Wei Zhao
2020-04-28  7:39     ` [dpdk-dev] [PATCH v3 2/3] doc: input set requirement of each pctype for FDIR Wei Zhao
2020-04-28  7:39     ` [dpdk-dev] [PATCH v3 3/3] net/i40e: remove teardown when flush FDIR filter Wei Zhao
2020-04-29  2:03     ` [dpdk-dev] [PATCH v4 0/3] fix i40e bug for flow filter Wei Zhao
2020-04-29  2:03       ` [dpdk-dev] [PATCH v4 1/3] net/i40e: fix FDIR issue for ARP packets Wei Zhao
2020-04-29  2:03       ` [dpdk-dev] [PATCH v4 2/3] doc: input set requirement of each pctype for FDIR Wei Zhao
2020-04-29 10:35         ` [dpdk-dev] [dpdk-stable] " Ferruh Yigit
2020-04-30  0:52           ` Zhao1, Wei [this message]
2020-04-30 10:19             ` Ferruh Yigit
2020-05-06  1:05               ` Zhao1, Wei
2020-05-06  9:29                 ` Ferruh Yigit
2020-05-06  9:32                   ` Zhao1, Wei
2020-04-29  2:03       ` [dpdk-dev] [PATCH v4 3/3] net/i40e: remove teardown when flush FDIR filter Wei Zhao
2020-04-29  3:05       ` [dpdk-dev] [PATCH v4 0/3] fix i40e bug for flow filter Xing, Beilei
2020-04-29  7:17         ` [dpdk-dev] [dpdk-stable] " Ye Xiaolong

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=MWHPR11MB1391B3E3C48DAB22454A3A05B7AA0@MWHPR11MB1391.namprd11.prod.outlook.com \
    --to=wei.zhao1@intel.com \
    --cc=beilei.xing@intel.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=maxime.leroy@6wind.com \
    --cc=stable@dpdk.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).