public inbox for netdev@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Ratheesh Kannoth <rkannoth@marvell.com>
Cc: netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	sgoutham@marvell.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, donald.hunter@gmail.com,
	jiri@resnulli.us, chuck.lever@oracle.com, matttbe@kernel.org,
	cjubran@nvidia.com, shshitrit@nvidia.com
Subject: Re: [PATCH v2 net-next 3/5] octeontx2-af: npc: cn20k: add subbank search order control
Date: Fri, 6 Mar 2026 14:24:34 +0000	[thread overview]
Message-ID: <20260306142434.GF461701@kernel.org> (raw)
In-Reply-To: <20260304043032.3661647-4-rkannoth@marvell.com>

On Wed, Mar 04, 2026 at 10:00:30AM +0530, Ratheesh Kannoth wrote:
> CN20K NPC MCAM is split into 32 subbanks that are searched in a
> predefined order during allocation. Lower-numbered subbanks have
> higher priority than higher-numbered ones.
> 
> Add a runtime devlink parameter "srch_order" (
> DEVLINK_PARAM_TYPE_U32_ARRAY) to control the order in which
> subbanks are searched during MCAM allocation.
> 
> Signed-off-by: Ratheesh Kannoth <rkannoth@marvell.com>
> ---
>  drivers/base/memory.c                         |  1 -
>  .../ethernet/marvell/octeontx2/af/cn20k/npc.c | 87 ++++++++++++++++++
>  .../ethernet/marvell/octeontx2/af/cn20k/npc.h |  2 +
>  .../marvell/octeontx2/af/rvu_devlink.c        | 92 +++++++++++++++++--
>  4 files changed, 171 insertions(+), 11 deletions(-)
> 
> diff --git a/drivers/base/memory.c b/drivers/base/memory.c
> index a3091924918b..88762061e0a1 100644
> --- a/drivers/base/memory.c
> +++ b/drivers/base/memory.c
> @@ -97,7 +97,6 @@ static void memory_block_release(struct device *dev)
>  	kfree(mem);
>  }
>  
> -
>  /* Max block size to be set by memory_block_advise_max_size */
>  static unsigned long memory_block_advised_size;
>  static bool memory_block_advised_size_queried;

Hi Ratheesh,

It looks like this hunk crept into this patch by mistake.

-- 
pw-bot: changes-requested

  reply	other threads:[~2026-03-06 14:24 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04  4:30 [PATCH v2 net-next 0/5] octeontx2-af: npc: Enhancements Ratheesh Kannoth
2026-03-04  4:30 ` [PATCH v2 net-next 1/5] octeontx2-af: npc: cn20k: debugfs enhancements Ratheesh Kannoth
2026-03-04  4:30 ` [PATCH v2 net-next 2/5] devlink: Implement devlink param multi attribute nested data values Ratheesh Kannoth
2026-03-04  4:30 ` [PATCH v2 net-next 3/5] octeontx2-af: npc: cn20k: add subbank search order control Ratheesh Kannoth
2026-03-06 14:24   ` Simon Horman [this message]
2026-03-04  4:30 ` [PATCH v2 net-next 4/5] octeontx2-af: npc: cn20k: dynamically allocate and free default MCAM entries Ratheesh Kannoth
2026-03-06 14:28   ` [v2,net-next,4/5] " Simon Horman
2026-03-04  4:30 ` [PATCH v2 net-next 5/5] octeontx2-af: Add support for loading custom KPU profile from filesystem Ratheesh Kannoth

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=20260306142434.GF461701@kernel.org \
    --to=horms@kernel.org \
    --cc=chuck.lever@oracle.com \
    --cc=cjubran@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=jiri@resnulli.us \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matttbe@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=rkannoth@marvell.com \
    --cc=sgoutham@marvell.com \
    --cc=shshitrit@nvidia.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