From: Christian Ehrhardt <christian.ehrhardt@canonical.com>
To: Satheesh Paul <psatheesh@marvell.com>
Cc: Jerin Jacob <jerinj@marvell.com>,
Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-stable] [PATCH 19.11] net/octeontx2: fix default MCAM allocation size
Date: Mon, 16 Aug 2021 10:52:56 +0200 [thread overview]
Message-ID: <CAATJJ0KzV-XxQYM0bmeMM+cDfmz5P3u-aw6vE8AJKzOmKgfPJg@mail.gmail.com> (raw)
In-Reply-To: <20210812112856.2772921-1-psatheesh@marvell.com>
On Thu, Aug 12, 2021 at 1:29 PM <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")
Thanks, applied
> 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 04da1abbdb..d29d1eb97b 100644
> --- a/drivers/net/octeontx2/otx2_ethdev_devargs.c
> +++ b/drivers/net/octeontx2/otx2_ethdev_devargs.c
> @@ -115,7 +115,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 scalar_enable = 0;
> --
> 2.25.4
>
--
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
prev parent reply other threads:[~2021-08-16 8:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-12 11:28 psatheesh
2021-08-16 8:52 ` Christian Ehrhardt [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=CAATJJ0KzV-XxQYM0bmeMM+cDfmz5P3u-aw6vE8AJKzOmKgfPJg@mail.gmail.com \
--to=christian.ehrhardt@canonical.com \
--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).