From: Jerin Jacob <jerinjacobk@gmail.com>
To: Satheesh Paul <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>, dpdk-dev <dev@dpdk.org>,
dpdk stable <stable@dpdk.org>
Subject: Re: [dpdk-dev] [PATCH] common/cnxk: fix log level during MCAM allocation
Date: Sat, 27 Aug 2022 18:17:35 +0530 [thread overview]
Message-ID: <CALBAE1NqYjzR3uRZ453Oqodk8rgzMOnKVfdM4-OEdYRT7yjtXQ@mail.gmail.com> (raw)
In-Reply-To: <20220705061356.3664923-1-psatheesh@marvell.com>
On Tue, Jul 5, 2022 at 11:44 AM <psatheesh@marvell.com> wrote:
>
> From: Satheesh Paul <psatheesh@marvell.com>
>
> Changed log level from info to debug for a log message
> printed during MCAM allocation.
>
> Fixes: 1f66919817ee ("common/cnxk: improve MCAM entries management")
> Cc: stable@dpdk.org
>
> Signed-off-by: Satheesh Paul <psatheesh@marvell.com>
> Reviewed-by: Kiran Kumar Kokkilagadda <kirankumark@marvell.com>
Applied to dpdk-next-net-mrvl/for-next-net. Thanks
> ---
> drivers/common/cnxk/roc_npc_utils.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/common/cnxk/roc_npc_utils.c b/drivers/common/cnxk/roc_npc_utils.c
> index cbc6200fec..8bdabc116d 100644
> --- a/drivers/common/cnxk/roc_npc_utils.c
> +++ b/drivers/common/cnxk/roc_npc_utils.c
> @@ -635,7 +635,7 @@ npc_alloc_mcam_by_ref_entry(struct mbox *mbox, struct roc_npc_flow *flow,
> npc_find_mcam_ref_entry(flow, npc, &prio, &ref_entry, dir);
> rc = npc_allocate_mcam_entry(mbox, prio, rsp_local, ref_entry);
> if (rc && !retry_done) {
> - plt_info(
> + plt_npc_dbg(
> "npc: Failed to allocate lower priority entry. Retrying for higher priority");
>
> dir = NPC_MCAM_HIGHER_PRIO;
> --
> 2.35.3
>
next prev parent reply other threads:[~2022-08-27 12:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-05 6:13 psatheesh
2022-08-27 12:47 ` Jerin Jacob [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-01-25 4:16 psatheesh
2022-02-17 7:21 ` Jerin Jacob
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=CALBAE1NqYjzR3uRZ453Oqodk8rgzMOnKVfdM4-OEdYRT7yjtXQ@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=psatheesh@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@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).