From: Jerin Jacob <jerinjacobk@gmail.com>
To: Ashwin Sekhar T K <asekhar@marvell.com>
Cc: dev@dpdk.org, Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>,
jerinj@marvell.com, pbhagavatula@marvell.com,
psatheesh@marvell.com, anoobj@marvell.com, gakhil@marvell.com,
hkalra@marvell.com
Subject: Re: [PATCH v2] common/cnxk: fix bp_ena clear while disabling aura
Date: Fri, 25 Aug 2023 11:22:56 +0530 [thread overview]
Message-ID: <CALBAE1Mx4z5gHiXHE+rJZUP2ctoR-k5H=8RkhAFAUkaSG_4B8Q@mail.gmail.com> (raw)
In-Reply-To: <20230825035721.2723124-1-asekhar@marvell.com>
On Fri, Aug 25, 2023 at 9:27 AM Ashwin Sekhar T K <asekhar@marvell.com> wrote:
>
> As done in FLR, similar to CQ disable, in process of
> aura disable we need to explicitly clear BP_ENA in order to
> deassert backpressure if it was earlier asserted.
>
> Fixes: f765f5611240 ("common/cnxk: add NPA pool HW operations")
>
> Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com>
> Signed-off-by: Ashwin Sekhar T K <asekhar@marvell.com>
Updated the git commit as follows and applied to
dpdk-next-net-mrvl/for-next-net. Thanks
common/cnxk: fix aura disable handling
As done in FLR, similar to CQ disable, in process of
aura disable we need to explicitly clear BP_ENA in order to
deassert backpressure if it was earlier asserted.
Fixes: f765f5611240 ("common/cnxk: add NPA pool HW operations")
Cc: stable@dpdk.org
Signed-off-by: Nithin Dabilpuram <ndabilpuram@marvell.com>
Signed-off-by: Ashwin Sekhar T K <asekhar@marvell.com>
prev parent reply other threads:[~2023-08-25 5:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-22 17:30 [PATCH] common/cnxk: explicitly clear aura bp ena on cleanup Ashwin Sekhar T K
2023-08-24 12:16 ` Jerin Jacob
2023-08-25 3:53 ` [PATCH] common/cnxk: fix bp_ena clearing during pool tear down Ashwin Sekhar T K
2023-08-25 3:57 ` [PATCH v2] common/cnxk: fix bp_ena clear while disabling aura Ashwin Sekhar T K
2023-08-25 5:52 ` 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='CALBAE1Mx4z5gHiXHE+rJZUP2ctoR-k5H=8RkhAFAUkaSG_4B8Q@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=anoobj@marvell.com \
--cc=asekhar@marvell.com \
--cc=dev@dpdk.org \
--cc=gakhil@marvell.com \
--cc=hkalra@marvell.com \
--cc=jerinj@marvell.com \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=pbhagavatula@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).