All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@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>,
	<jerinj@marvell.com>, <edumazet@google.com>, <pabeni@redhat.comi>,
	<jiri@resnulli.us>, <corbet@lwn.net>, <linux-doc@vger.kernel.org>
Subject: Re: [PATCH v4 net-next 3/3] devlink: Add documenation for OcteonTx2 AF
Date: Sun, 3 Nov 2024 11:55:48 -0800	[thread overview]
Message-ID: <20241103115548.35d0cbdf@kernel.org> (raw)
In-Reply-To: <20241029035739.1981839-4-lcherian@marvell.com>

On Tue, 29 Oct 2024 09:27:39 +0530 Linu Cherian wrote:
> +   * - ``npc_def_rule_cntr``
> +     - bool
> +     - runtime
> +     - Use to enable or disable hit counters for the default rules in NPC MCAM.

How are those counters accessible? ethtool -S? debugfs ? it should be
documented here. Plus please add examples of what such rules cover.
"default rules in NPC MCAM" requires too much familiarity with the
device.

  parent reply	other threads:[~2024-11-03 19:55 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-29  3:57 [PATCH v4 net-next 0/3] Knobs for NPC default rule counters Linu Cherian
2024-10-29  3:57 ` [PATCH v4 net-next 1/3] octeontx2-af: Refactor few NPC mcam APIs Linu Cherian
2024-10-29  3:57 ` [PATCH v4 net-next 2/3] octeontx2-af: Knobs for NPC default rule counters Linu Cherian
2024-11-02 14:54   ` Simon Horman
2024-11-03 19:53   ` Jakub Kicinski
2024-11-04 10:28     ` Linu Cherian
2024-10-29  3:57 ` [PATCH v4 net-next 3/3] devlink: Add documenation for OcteonTx2 AF Linu Cherian
2024-11-02 14:52   ` Simon Horman
2024-11-03 19:55   ` Jakub Kicinski [this message]
2024-11-04 10:33     ` Linu Cherian

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=20241103115548.35d0cbdf@kernel.org \
    --to=kuba@kernel.org \
    --cc=corbet@lwn.net \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gakula@marvell.com \
    --cc=hkelam@marvell.com \
    --cc=jerinj@marvell.com \
    --cc=jiri@resnulli.us \
    --cc=lcherian@marvell.com \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.comi \
    --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.