From: Simon Horman <horms@kernel.org>
To: Srujana Challa <schalla@marvell.com>
Cc: netdev@vger.kernel.org, davem@davemloft.net, kuba@kernel.org,
pabeni@redhat.com, edumazet@google.com, sgoutham@marvell.com,
lcherian@marvell.com, gakula@marvell.com, jerinj@marvell.com,
hkelam@marvell.com, sbhatta@marvell.com, bbhushan2@marvell.com,
ndabilpuram@marvell.com
Subject: Re: [PATCH net-next,v2,3/3] octeontx2-af: configure default CPT credits for CN10KA B0
Date: Fri, 30 Aug 2024 18:10:14 +0100 [thread overview]
Message-ID: <20240830171014.GB1368797@kernel.org> (raw)
In-Reply-To: <20240829080935.371281-4-schalla@marvell.com>
On Thu, Aug 29, 2024 at 01:39:35PM +0530, Srujana Challa wrote:
> The maximum CPT credits that RXC can use are now configurable on CN10KA B0
> through a hardware CSR. This patch sets the default value to optimize peak
> performance, aligning it with other chip versions.
>
> Signed-off-by: Srujana Challa <schalla@marvell.com>
Reviewed-by: Simon Horman <horms@kernel.org>
next prev parent reply other threads:[~2024-08-30 17:10 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-29 8:09 [PATCH net-next,v2,0/3] octeontx2-af: update CPT block for CN10KB and CN10KA B0 Srujana Challa
2024-08-29 8:09 ` [PATCH net-next,v2,1/3] octeontx2-af: use dynamic interrupt vectors for CN10K Srujana Challa
2024-08-30 17:09 ` Simon Horman
2024-08-29 8:09 ` [PATCH net-next,v2,2/3] octeontx2-af: avoid RXC register access for CN10KB Srujana Challa
2024-08-30 17:09 ` Simon Horman
2024-08-29 8:09 ` [PATCH net-next,v2,3/3] octeontx2-af: configure default CPT credits for CN10KA B0 Srujana Challa
2024-08-30 17:10 ` Simon Horman [this message]
2024-09-01 17:20 ` [PATCH net-next,v2,0/3] octeontx2-af: update CPT block for CN10KB and " patchwork-bot+netdevbpf
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=20240830171014.GB1368797@kernel.org \
--to=horms@kernel.org \
--cc=bbhushan2@marvell.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=gakula@marvell.com \
--cc=hkelam@marvell.com \
--cc=jerinj@marvell.com \
--cc=kuba@kernel.org \
--cc=lcherian@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sbhatta@marvell.com \
--cc=schalla@marvell.com \
--cc=sgoutham@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.