From: "Chen, BoX C" <box.c.chen@intel.com>
To: "Xing, Beilei" <beilei.xing@intel.com>,
"Amber, Kumar" <kumar.amber@intel.com>,
"dev@dpdk.org" <dev@dpdk.org>
Cc: "Zhao1, Wei" <wei.zhao1@intel.com>
Subject: Re: [dpdk-dev] [PATCH v2] net/i40e: fix argument in RSS action
Date: Thu, 17 Dec 2020 09:06:13 +0000 [thread overview]
Message-ID: <DM6PR11MB30997BBD4B6C1A72A2E46F2CD9C40@DM6PR11MB3099.namprd11.prod.outlook.com> (raw)
In-Reply-To: <MN2PR11MB3807A808259E4F72267DF326F7C40@MN2PR11MB3807.namprd11.prod.outlook.com>
Hi, Beilei
If you merge this patch, some common rules will fail to set on fvl, such as:
flow create 0 ingress pattern eth / ipv4 / udp / end actions rss types ipv4-udp end queues end / end
Regards,
Chen Bo
> -----Original Message-----
> From: Xing, Beilei <beilei.xing@intel.com>
> Sent: December 17, 2020 11:20
> To: Amber, Kumar <kumar.amber@intel.com>; dev@dpdk.org; Chen, BoX C
> <box.c.chen@intel.com>
> Cc: Zhao1, Wei <wei.zhao1@intel.com>
> Subject: RE: [dpdk-dev] [PATCH v2] net/i40e: fix argument in RSS action
>
> Hi,
>
> According to Bo's test, this fix patch will cause other cases fail, so NACK.
> @Bo, could you please detail which cases will FAIL, thanks.
>
> BR,
> Beilei
>
> > -----Original Message-----
> > From: dev <dev-bounces@dpdk.org> On Behalf Of Kumar Amber
> > Sent: Wednesday, November 11, 2020 6:11 PM
> > To: dev@dpdk.org
> > Cc: Zhao1, Wei <wei.zhao1@intel.com>
> > Subject: [dpdk-dev] [PATCH v2] net/i40e: fix argument in RSS action
> >
> > The driver must check for the queue number in the RSS action list and
> > if not should return with a proper error message to user.
> >
> > Bugzilla ID: 573
> > Fixes: 9486d60b94b5 ("net/i40e: fix flow RSS queue index check")
> > Cc: wei.zhao1@intel.com
> >
> > Signed-off-by: Kumar Amber <kumar.amber@intel.com>
> > ---
> > drivers/net/i40e/i40e_flow.c | 11 +++++++++++
> > 1 file changed, 11 insertions(+)
> >
> > diff --git a/drivers/net/i40e/i40e_flow.c
> > b/drivers/net/i40e/i40e_flow.c index 5bec0c7a84..975340cb1a 100644
> > --- a/drivers/net/i40e/i40e_flow.c
> > +++ b/drivers/net/i40e/i40e_flow.c
> > @@ -4917,6 +4917,17 @@ i40e_flow_parse_rss_action(struct rte_eth_dev
> > *dev,
> > NEXT_ITEM_OF_ACTION(act, actions, index);
> > rss = act->conf;
> >
> > + /**
> > + * Check if Queue number is specified
> > + * in argument else throw an error.
> > + */
> > + if (rss->queue == NULL) {
> > + rte_flow_error_set(error, EINVAL,
> > + RTE_FLOW_ERROR_TYPE_ACTION,
> > + act, "Queue numbers not given.");
> > + return -rte_errno;
> > + }
> > +
> > /**
> > * RSS only supports forwarding,
> > * check if the first not void action is RSS.
> > --
> > 2.17.1
prev parent reply other threads:[~2020-12-17 9:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 18:04 [dpdk-dev] [PATCH v1] net/i40e: argument in RSS action should have queue Kumar Amber
2020-11-11 10:10 ` [dpdk-dev] [PATCH v2] net/i40e: fix argument in RSS action Kumar Amber
2020-11-12 10:41 ` [dpdk-dev] [PATCH v3] " Kumar Amber
2020-11-12 10:42 ` [dpdk-dev] [PATCH v4] " Kumar Amber
2020-12-24 1:00 ` Zhang, Qi Z
2021-01-04 10:04 ` Amber, Kumar
2020-12-17 3:20 ` [dpdk-dev] [PATCH v2] " Xing, Beilei
2020-12-17 9:06 ` Chen, BoX C [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=DM6PR11MB30997BBD4B6C1A72A2E46F2CD9C40@DM6PR11MB3099.namprd11.prod.outlook.com \
--to=box.c.chen@intel.com \
--cc=beilei.xing@intel.com \
--cc=dev@dpdk.org \
--cc=kumar.amber@intel.com \
--cc=wei.zhao1@intel.com \
/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).