[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e7a0df7c16d72f0d565521c76cd4f30142d57ccb.camel@kernel.org>
Date: Thu, 12 Nov 2020 11:48:00 -0800
From: Saeed Mahameed <saeed@...nel.org>
To: Naveen Mamindlapalli <naveenm@...vell.com>, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: kuba@...nel.org, davem@...emloft.net, sgoutham@...vell.com,
lcherian@...vell.com, gakula@...vell.com, jerinj@...vell.com,
sbhatta@...vell.com, hkelam@...vell.com
Subject: Re: [PATCH v3 net-next 07/13] octeontx2-af: Add debugfs entry to
dump the MCAM rules
On Wed, 2020-11-11 at 12:43 +0530, Naveen Mamindlapalli wrote:
> From: Subbaraya Sundeep <sbhatta@...vell.com>
>
> Add debugfs support to dump the MCAM rules installed using
> NPC_INSTALL_FLOW mbox message. Debugfs file can display mcam
> entry, counter if any, flow type and counter hits.
>
> Ethtool will dump the ntuple flows related to the PF only.
> The debugfs file gives systemwide view of the MCAM rules
> installed by all the PF's.
>
> Below is the example output when the debugfs file is read:
> ~ # mount -t debugfs none /sys/kernel/debug
> ~ # cat /sys/kernel/debug/octeontx2/npc/mcam_rules
>
> Installed by: PF1
> direction: RX
> mcam entry: 227
> udp source port 23 mask 0xffff
> Forward to: PF1 VF0
> action: Direct to queue 0
> enabled: yes
> counter: 1
> hits: 0
>
I don't want to block this series or anything, but you might want to
use devlink dpipe interface for this:
https://www.kernel.org/doc/html/latest/networking/devlink/devlink-dpipe.html
As a future patch of course.
Thanks,
Saeed.
Powered by blists - more mailing lists