public inbox for netdev@vger.kernel.org 
 help / color / mirror / Atom feed
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,2/2] octeontx2-af: configure default CPT credits
Date: Tue, 27 Aug 2024 17:37:33 +0100	[thread overview]
Message-ID: <20240827163733.GP1368797@kernel.org> (raw)
In-Reply-To: <20240827042512.216634-3-schalla@marvell.com>

On Tue, Aug 27, 2024 at 09:55:12AM +0530, Srujana Challa wrote:
> The maximum CPT credits that RX can use are now configurable through
> a hardware CSR. This patch sets the default value to optimize peak
> performance, aligning it with other chip versions.
> This patch also adds changes to avoid RXC HW registers access on
> CN10KB as RXC is not available on CN10KB.

This sounds like it should be split into two patches.

> Signed-off-by: Srujana Challa <schalla@marvell•com>
> Signed-off-by: Nithin Kumar Dabilpuram <ndabilpuram@marvell•com>

...

      reply	other threads:[~2024-08-27 16:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-27  4:25 [PATCH net-next,0/2] octeontx2-af: Update CPT block for CN10KB Srujana Challa
2024-08-27  4:25 ` [PATCH net-next,1/2] octeontx2-af: reduce cpt flt interrupt vectors " Srujana Challa
2024-08-27 16:32   ` Simon Horman
2024-08-28  5:39     ` [EXTERNAL] " Srujana Challa
2024-08-27  4:25 ` [PATCH net-next,2/2] octeontx2-af: configure default CPT credits Srujana Challa
2024-08-27 16:37   ` Simon Horman [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=20240827163733.GP1368797@kernel.org \
    --to=horms@kernel$(echo .)org \
    --cc=bbhushan2@marvell$(echo .)com \
    --cc=davem@davemloft$(echo .)net \
    --cc=edumazet@google$(echo .)com \
    --cc=gakula@marvell$(echo .)com \
    --cc=hkelam@marvell$(echo .)com \
    --cc=jerinj@marvell$(echo .)com \
    --cc=kuba@kernel$(echo .)org \
    --cc=lcherian@marvell$(echo .)com \
    --cc=ndabilpuram@marvell$(echo .)com \
    --cc=netdev@vger$(echo .)kernel.org \
    --cc=pabeni@redhat$(echo .)com \
    --cc=sbhatta@marvell$(echo .)com \
    --cc=schalla@marvell$(echo .)com \
    --cc=sgoutham@marvell$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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