From: Andrew Lunn <andrew@lunn.ch>
To: Vladimir Oltean <vladimir.oltean@nxp.com>
Cc: Steven Rostedt <rostedt@goodmis.org>,
Florian Fainelli <f.fainelli@gmail.com>,
Masami Hiramatsu <mhiramat@kernel.org>,
netdev@vger.kernel.org, Jakub Kicinski <kuba@kernel.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Paolo Abeni <pabeni@redhat.com>
Subject: Re: [PATCH net-next 0/2] DSA trace events
Date: Thu, 27 Apr 2023 02:33:56 +0200 [thread overview]
Message-ID: <2f150ad4-34f4-4af9-b3ce-c1aff208ec7e@lunn.ch> (raw)
In-Reply-To: <20230426194301.mtw2d5ooi3ywtxad@skbuf>
> Well, there's one thing that could become useful for tooling, and
> that's determining the resource utilization of the hardware (number of
> dsa_fdb_add_hw events minus dsa_fdb_del_hw, number of dsa_vlan_add_hw
> minus dsa_vlan_del_hw, etc) relative to some hardcoded maximum capacity
> which would be somehow determined by userspace for each driver. There
> have been requests for this in the not so distant past.
That sounds similar to devlink resources. The mv88e6xxx driver already
returns the number of entries in the ATU, and the size of the
ATU. Maybe that just needs generalising?
Andrew
next prev parent reply other threads:[~2023-04-27 0:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-07 14:14 [PATCH net-next 0/2] DSA trace events Vladimir Oltean
2023-04-07 14:14 ` [PATCH net-next 1/2] net: dsa: add trace points for FDB/MDB operations Vladimir Oltean
2023-04-07 14:14 ` [PATCH net-next 2/2] net: dsa: add trace points for VLAN operations Vladimir Oltean
2023-04-12 0:48 ` [PATCH net-next 0/2] DSA trace events Andrew Lunn
2023-04-12 9:55 ` Vladimir Oltean
2023-04-21 12:38 ` Masami Hiramatsu
2023-04-21 12:47 ` Vladimir Oltean
2023-04-24 22:25 ` Steven Rostedt
2023-04-26 19:13 ` Vladimir Oltean
2023-04-26 19:23 ` Steven Rostedt
2023-04-26 19:43 ` Vladimir Oltean
2023-04-26 19:47 ` Steven Rostedt
2023-04-26 21:07 ` Vladimir Oltean
2023-04-27 0:33 ` Andrew Lunn [this message]
2023-04-12 8:30 ` 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=2f150ad4-34f4-4af9-b3ce-c1aff208ec7e@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=f.fainelli@gmail.com \
--cc=kuba@kernel.org \
--cc=mhiramat@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rostedt@goodmis.org \
--cc=vladimir.oltean@nxp.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