From: Jerin Jacob <jerinjacobk@gmail.com>
To: Kiran Kumar K <kirankumark@marvell.com>,
Ferruh Yigit <ferruh.yigit@intel.com>
Cc: Jerin Jacob <jerinj@marvell.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
dpdk-dev <dev@dpdk.org>, dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [dpdk-dev] [PATCH] net/octeontx2: fix rss flow create
Date: Sun, 11 Oct 2020 15:07:32 +0530 [thread overview]
Message-ID: <CALBAE1PPc4Xm+nPyGHrsg89rJZpF-SHAOBSvxPz059nf5DMkXA@mail.gmail.com> (raw)
In-Reply-To: <20201010063310.809945-1-kirankumark@marvell.com>
On Sat, Oct 10, 2020 at 12:03 PM <kirankumark@marvell.com> wrote:
>
> From: Kiran Kumar K <kirankumark@marvell.com>
>
> While creating flow with action type RSS, action type is not being
> set to RSS, and action type is being set to unicast. Therefore it breaks
> RSS functionality. This patch add changes to program the RSS action
> properly.
>
> Fixes: 4092e4845d ("net/octeontx2: add flow operations")
Cc: stable@dpdk.org
Applied to dpdk-next-net-mrvl/for-main. Thanks.
>
> Signed-off-by: Kiran Kumar K <kirankumark@marvell.com>
> ---
> drivers/net/octeontx2/otx2_flow.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/net/octeontx2/otx2_flow.c b/drivers/net/octeontx2/otx2_flow.c
> index 13a76e441..90540ffbd 100644
> --- a/drivers/net/octeontx2/otx2_flow.c
> +++ b/drivers/net/octeontx2/otx2_flow.c
> @@ -270,6 +270,8 @@ flow_program_rss_action(struct rte_eth_dev *eth_dev,
> if (rc)
> return rc;
>
> + flow->npc_action &= (~(0xfULL));
> + flow->npc_action |= NIX_RX_ACTIONOP_RSS;
> flow->npc_action |=
> ((uint64_t)(alg_idx & NIX_RSS_ACT_ALG_MASK) <<
> NIX_RSS_ACT_ALG_OFFSET) |
> --
> 2.25.1
>
parent reply other threads:[~2020-10-11 9:37 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <20201010063310.809945-1-kirankumark@marvell.com>]
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=CALBAE1PPc4Xm+nPyGHrsg89rJZpF-SHAOBSvxPz059nf5DMkXA@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.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).