From: Jerin Jacob <jerinjacobk@gmail.com>
To: psatheesh@marvell.com
Cc: Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>,
dev@dpdk.org, Jerin Jacob <jerinj@marvell.com>
Subject: Re: [dpdk-dev] [PATCH 1/2] common/cnxk: limit RSS key config with RTE Flow operations
Date: Wed, 20 Sep 2023 09:16:55 +0530 [thread overview]
Message-ID: <CALBAE1NXJN3jQBezuVZqmxvNCcqaofHRNkKC=bzWLBrd7JrsWg@mail.gmail.com> (raw)
In-Reply-To: <20230904105742.1159342-1-psatheesh@marvell.com>
On Mon, Sep 4, 2023 at 4:27 PM <psatheesh@marvell.com> wrote:
>
> From: Kiran Kumar K <kirankumark@marvell.com>
>
> Limit the configuring RSS key with RTE Flow operations for cnxk
> device. Key can be update only with dev operations using
> rte_eth_dev_rss_hash_update.
>
> Signed-off-by: Kiran Kumar K <kirankumark@marvell.com>
> Reviewed-by: Jerin Jacob <jerinj@marvell.com>
Updated the git commit for 1/2 patch as follows and applied to
dpdk-next-net-mrvl/for-next-net. Thanks
2/2 patch can be merged along with port representor changes.
Holding2/2 patch now.
common/cnxk: fix RSS key configuration
Limit the configuring RSS key with rte_flow operations as
it is a global resource. Key can be update only with ethdev dev
operations using rte_eth_dev_rss_hash_update().
Fixes: 51dc6a80f843 ("common/cnxk: support RSS action in NPC rule")
Cc: stable@dpdk.org
Signed-off-by: Kiran Kumar K <kirankumark@marvell.com>
Reviewed-by: Jerin Jacob <jerinj@marvell.com>
prev parent reply other threads:[~2023-09-20 3:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-04 10:57 psatheesh
2023-09-04 10:57 ` [dpdk-dev] [PATCH 2/2] drivers: add represented port flow item for cnxk psatheesh
2023-12-05 11:53 ` [dpdk-dev] [PATCH v2] " psatheesh
2023-09-20 3:46 ` Jerin Jacob [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='CALBAE1NXJN3jQBezuVZqmxvNCcqaofHRNkKC=bzWLBrd7JrsWg@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=psatheesh@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@marvell.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).