DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Zhao1, Wei" <wei.zhao1@intel.com>
To: "Zhang, Qi Z" <qi.z.zhang@intel.com>,
	"dev@dpdk.org" <dev@dpdk.org>,
	"stable@dpdk.org" <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] net/i40e: add flow RSS queue index check
Date: Wed, 4 Apr 2018 04:02:20 +0000	[thread overview]
Message-ID: <A2573D2ACFCADC41BB3BE09C6DE313CA07CFEAE1@PGSMSX101.gar.corp.intel.com> (raw)
In-Reply-To: <039ED4275CED7440929022BC67E706115318212C@SHSMSX103.ccr.corp.intel.com>

Ok,I will add more comment in other  independent patch

> -----Original Message-----
> From: Zhang, Qi Z
> Sent: Wednesday, April 4, 2018 11:59 AM
> To: Zhao1, Wei <wei.zhao1@intel.com>; dev@dpdk.org; stable@dpdk.org
> Subject: RE: [PATCH] net/i40e: add flow RSS queue index check
> 
> 
> 
> > -----Original Message-----
> > From: Zhao1, Wei
> > Sent: Wednesday, April 4, 2018 11:19 AM
> > To: dev@dpdk.org; stable@dpdk.org
> > Cc: Zhang, Qi Z <qi.z.zhang@intel.com>; Zhao1, Wei
> > <wei.zhao1@intel.com>
> > Subject: [PATCH] net/i40e: add flow RSS queue index check
> >
> > There need a queue index check for RSS queue region in order to aviod
> > error from configuration.
> >
> > Fixes: ecad87d22383 ("net/i40e: move RSS to flow API")
> > Signed-off-by: Wei Zhao <wei.zhao1@intel.com>
> > Tested-by: Peng Yuan <yuan.peng@intel.com>
> 
> Please add Cc: stable@dpdk.org here.
> 
> > ---
> >  drivers/net/i40e/i40e_flow.c | 14 ++++++++++++++
> >  1 file changed, 14 insertions(+)
> >
> > diff --git a/drivers/net/i40e/i40e_flow.c
> > b/drivers/net/i40e/i40e_flow.c index f3e8c5f..4e86ecb 100644
> > --- a/drivers/net/i40e/i40e_flow.c
> > +++ b/drivers/net/i40e/i40e_flow.c
> > @@ -4249,6 +4249,20 @@ i40e_flow_parse_rss_action(struct rte_eth_dev
> > *dev,
> >  				return -rte_errno;
> >  			}
> >
> > +			for (i = 0; i < rss->num; i++) {
> > +				for (j = 0; j < rss_info->num; j++) {
> > +					if (rss->queue[i] == rss_info-
> >queue[j])
> > +						break;
> > +				}
> > +				if (j == rss_info->num) {
> > +					rte_flow_error_set(error, EINVAL,
> > +
> 	RTE_FLOW_ERROR_TYPE_ACTION,
> > +						act,
> > +						"no valid queues");
> > +					return -rte_errno;
> > +				}
> > +			}
> 
> Is it necessary to add this check inside the big loop ?
> 
> Btw, the function of i40e_flow_parse_rss_action looks too big and without
> enough comment
> 
> It's better to use sub-function or add some comment before each code block
> to make it more readable.
> 
> Regards
> Qi
> 
> 
> > +
> >  			for (i = 0; i < info->queue_region_number; i++) {
> >  				if (info->region[i].queue_num == rss->num
> &&
> >  					info->region[i].queue_start_index ==
> > --
> > 2.7.5


  reply	other threads:[~2018-04-04  4:04 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-04  3:18 Wei Zhao
2018-04-04  3:59 ` Zhang, Qi Z
2018-04-04  4:02   ` Zhao1, Wei [this message]
2018-04-04  5:12   ` Zhao1, Wei
2018-04-04  5:00 ` [dpdk-dev] [PATCH v2] " Wei Zhao
2018-04-04  5:06   ` [dpdk-dev] [PATCH v3] " Wei Zhao
2018-04-04  8:06     ` [dpdk-dev] [PATCH v4] " Wei Zhao
2018-04-04 13:25       ` Zhang, Qi Z
2018-04-06  8:30         ` Zhang, Helin

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=A2573D2ACFCADC41BB3BE09C6DE313CA07CFEAE1@PGSMSX101.gar.corp.intel.com \
    --to=wei.zhao1@intel.com \
    --cc=dev@dpdk.org \
    --cc=qi.z.zhang@intel.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).