All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Horman <horms@kernel.org>
To: Linu Cherian <lcherian@marvell.com>
Cc: davem@davemloft.net, sgoutham@marvell.com,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	gakula@marvell.com, hkelam@marvell.com, sbhatta@marvell.com,
	edumazet@google.com, kuba@kernel.org, pabeni@redhat.com
Subject: Re: [PATCH v2 net-next 1/2] octeontx2-af: Knobs for NPC default rule counters
Date: Tue, 17 Sep 2024 09:12:44 +0100	[thread overview]
Message-ID: <20240917081244.GK167971@kernel.org> (raw)
In-Reply-To: <20240917043826.GA720400@hyd1403.caveonetworks.com>

On Tue, Sep 17, 2024 at 10:08:26AM +0530, Linu Cherian wrote:
> Hi Simon,
> 
> On 2024-09-14 at 13:43:17, Simon Horman (horms@kernel.org) wrote:
> > On Thu, Sep 12, 2024 at 09:44:49PM +0530, Linu Cherian wrote:
> > > Add devlink knobs to enable/disable counters on NPC
> > > default rule entries.
> > > 
> > > Introduce lowlevel variant of rvu_mcam_remove/add_counter_from/to_rule
> > > for better code reuse, which assumes necessary locks are taken at
> > > higher level.
> > > 
> > > Sample command to enable default rule counters:
> > > devlink dev param set <dev> name npc_def_rule_cntr value true cmode runtime
> > > 
> > > Sample command to read the counter:
> > > cat /sys/kernel/debug/cn10k/npc/mcam_rules
> > > 
> > > Signed-off-by: Linu Cherian <lcherian@marvell.com>
> > > ---
> > > Changelog from v1:
> > > Removed wrong mutex_unlock invocations.
> > 
> > Hi Linu,
> > 
> > This patch seems to be doing two things:
> > 
> > 1) Refactoring some functions to have locking and non-locking variants.
> >    By LoC this is appears the bulk of the code changed in this patch.
> >    It also appears to be straightforward.
> > 
> > 2) Adding devlink knobs
> > 
> >    As this is a user-facing change it probably requires a deeper review
> >    than 1)
> > 
> > I would suggest, that for review, it would be very nice to split
> > 1) and 2) into separate patches. Maybe including a note in the patch
> > for 1) that the refactor will be used in the following patch for 2).
> >
> 
> Ack. Will split into two while reposting.

Thanks.

Please note that net-next is currently closed for the v6.12 merge window.
So please wait for it to re-open before reposting. That will occur
after v6.12-rc1 is released, most likely about two weeks from now.

> 
> > As for the code changes themselves, I did look over them,
> > and I didn't see any problems.
> 
> 
> Linu Cherian.
> 

  reply	other threads:[~2024-09-17  8:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-12 16:14 [PATCH v2 net-next 0/2] octeontx2: Few debugfs enhancements Linu Cherian
2024-09-12 16:14 ` [PATCH v2 net-next 1/2] octeontx2-af: Knobs for NPC default rule counters Linu Cherian
2024-09-14  8:13   ` Simon Horman
2024-09-17  4:38     ` Linu Cherian
2024-09-17  8:12       ` Simon Horman [this message]
2024-09-12 16:14 ` [PATCH v2 net-next 2/2] octeontx2-af: debugfs: Add Channel info to RPM map Linu Cherian
2024-09-14  4:43 ` [PATCH v2 net-next 0/2] octeontx2: Few debugfs enhancements Jakub Kicinski
2024-09-14  4:50 ` 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=20240917081244.GK167971@kernel.org \
    --to=horms@kernel.org \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gakula@marvell.com \
    --cc=hkelam@marvell.com \
    --cc=kuba@kernel.org \
    --cc=lcherian@marvell.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=sbhatta@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.