From: "Zhang, Qi Z" <qi.z.zhang@intel.com>
To: "Zhao1, Wei" <wei.zhao1@intel.com>, "dev@dpdk.org" <dev@dpdk.org>
Cc: "stable@dpdk.org" <stable@dpdk.org>,
"Peng, Yuan" <yuan.peng@intel.com>,
"Li, WenjieX A" <wenjiex.a.li@intel.com>
Subject: Re: [dpdk-dev] [PATCH] net/i40e: fix error when create two RSS flow rule
Date: Tue, 14 May 2019 12:58:34 +0000 [thread overview]
Message-ID: <039ED4275CED7440929022BC67E7061153381303@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <A2573D2ACFCADC41BB3BE09C6DE313CA07EE5117@PGSMSX103.gar.corp.intel.com>
> -----Original Message-----
> From: Zhao1, Wei
> Sent: Thursday, May 9, 2019 11:35 AM
> To: dev@dpdk.org
> Cc: stable@dpdk.org; Zhang, Qi Z <qi.z.zhang@intel.com>; Peng, Yuan
> <yuan.peng@intel.com>; Li, WenjieX A <wenjiex.a.li@intel.com>
> Subject: RE: [PATCH] net/i40e: fix error when create two RSS flow rule
>
> Tested-by: Li WenjieX <wenjiex.a.li@intel.com>
>
> > -----Original Message-----
> > From: Zhao1, Wei
> > Sent: Thursday, May 9, 2019 11:00 AM
> > To: dev@dpdk.org
> > Cc: stable@dpdk.org; Zhang, Qi Z <qi.z.zhang@intel.com>; Peng, Yuan
> > <yuan.peng@intel.com>; Zhao1, Wei <wei.zhao1@intel.com>
> > Subject: [PATCH] net/i40e: fix error when create two RSS flow rule
> >
> > There is need to refuse to create the second RSS flow rule as only one
> > RSS key and HASH register for each PF port.
> > Users should delete the first rule before setup the second rule.
> >
> > Fixes: ecad87d22383 ("net/i40e: move RSS to flow API")
> > Cc: stable@dpdk.org
> >
> > Signed-off-by: Wei Zhao <wei.zhao1@intel.com>
Acked-by: Qi Zhang <qi.z.zhang@intel.com>
Applied to dpdk-next-net-intel.
Thanks
Qi
next prev parent reply other threads:[~2019-05-14 12:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-09 2:59 Wei Zhao
2019-05-09 2:59 ` Wei Zhao
2019-05-09 3:34 ` Zhao1, Wei
2019-05-09 3:34 ` Zhao1, Wei
2019-05-14 12:58 ` Zhang, Qi Z [this message]
2019-05-14 12:58 ` Zhang, Qi Z
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=039ED4275CED7440929022BC67E7061153381303@SHSMSX103.ccr.corp.intel.com \
--to=qi.z.zhang@intel.com \
--cc=dev@dpdk.org \
--cc=stable@dpdk.org \
--cc=wei.zhao1@intel.com \
--cc=wenjiex.a.li@intel.com \
--cc=yuan.peng@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).