From: Paolo Abeni <pabeni@redhat.com>
To: Sai Krishna <saikrishnag@marvell.com>,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
sgoutham@marvell.com, sumang@marvell.com
Subject: Re: [net PATCH] octeontx2-af: Unlock contexts in the queue context cache in case of fault detection
Date: Thu, 23 Feb 2023 10:52:12 +0100 [thread overview]
Message-ID: <8e05cf636937ad59e32b4ae7f1e7e8732c694421.camel@redhat.com> (raw)
In-Reply-To: <20230222065921.1852686-1-saikrishnag@marvell.com>
On Wed, 2023-02-22 at 12:29 +0530, Sai Krishna wrote:
> From: Suman Ghosh <sumang@marvell.com>
>
> NDC caches contexts of frequently used queue's (Rx and Tx queues)
> contexts. Due to a HW errata when NDC detects fault/poision while
> accessing contexts it could go into an illegal state where a cache
> line could get locked forever. To makesure all cache lines in NDC
> are available for optimum performance upon fault/lockerror/posion
> errors scan through all cache lines in NDC and clear the lock bit.
>
> Fixes: 4a3581cd5995 ("octeontx2-af: NPA AQ instruction enqueue support")
> Signed-off-by: Suman Ghosh <sumang@marvell.com>
> Signed-off-by: Sunil Kovvuri Goutham <sgoutham@marvell.com>
> Signed-off-by: Sai Krishna <saikrishnag@marvell.com>
After the net-next merge, this does not apply cleanly to net anymore.
Please rebase and re-post, thanks!
Paolo
prev parent reply other threads:[~2023-02-23 9:53 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 6:59 [net PATCH] octeontx2-af: Unlock contexts in the queue context cache in case of fault detection Sai Krishna
2023-02-23 9:52 ` Paolo Abeni [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=8e05cf636937ad59e32b4ae7f1e7e8732c694421.camel@redhat.com \
--to=pabeni@redhat.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@vger.kernel.org \
--cc=saikrishnag@marvell.com \
--cc=sgoutham@marvell.com \
--cc=sumang@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).