From: Luca Boccassi <bluca@debian.org>
To: psatheesh@marvell.com, Jerin Jacob <jerinj@marvell.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>
Cc: stable@dpdk.org
Subject: Re: [dpdk-stable] [PATCH 20.11] net/octeontx2: fix default MCAM allocation size
Date: Thu, 29 Jul 2021 09:36:18 +0100 [thread overview]
Message-ID: <0ee91b303c2afba34820499a7597b0ac191d98a8.camel@debian.org> (raw)
In-Reply-To: <20210729041356.2053698-1-psatheesh@marvell.com>
On Thu, 2021-07-29 at 09:43 +0530, psatheesh@marvell.com wrote:
> From: Satheesh Paul <psatheesh@marvell.com>
>
> [ upstream commit d81cea5280112f5f6c8796c2fb0bad72bf29d41e ]
>
> Preallocation of MCAM entries is not valid anymore since the
> AF side MCAM allocation scheme has changed. This patch disables
> preallocation by changing the default MCAM preallocation size
> from 8 to 1.
>
> Fixes: 168c59cfe42 ("net/octeontx2: add flow MCAM utility functions")
>
> Signed-off-by: Satheesh Paul <psatheesh@marvell.com>
> ---
> drivers/net/octeontx2/otx2_ethdev_devargs.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/net/octeontx2/otx2_ethdev_devargs.c b/drivers/net/octeontx2/otx2_ethdev_devargs.c
> index d4a85bf55e..3f9542331f 100644
> --- a/drivers/net/octeontx2/otx2_ethdev_devargs.c
> +++ b/drivers/net/octeontx2/otx2_ethdev_devargs.c
> @@ -134,7 +134,7 @@ otx2_ethdev_parse_devargs(struct rte_devargs *devargs, struct otx2_eth_dev *dev)
> {
> uint16_t rss_size = NIX_RSS_RETA_SIZE;
> uint16_t sqb_count = NIX_MAX_SQB;
> - uint16_t flow_prealloc_size = 8;
> + uint16_t flow_prealloc_size = 1;
> uint16_t switch_header_type = 0;
> uint16_t flow_max_priority = 3;
> uint16_t ipsec_in_max_spi = 1;
Acked-by: Luca Boccassi <bluca@debian.org>
Thanks, applied and pushed.
--
Kind regards,
Luca Boccassi
prev parent reply other threads:[~2021-07-29 8:36 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-29 4:13 psatheesh
2021-07-29 8:36 ` Luca Boccassi [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=0ee91b303c2afba34820499a7597b0ac191d98a8.camel@debian.org \
--to=bluca@debian.org \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=psatheesh@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).