[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <2f150ad4-34f4-4af9-b3ce-c1aff208ec7e@lunn.ch>
Date: Thu, 27 Apr 2023 02:33:56 +0200
From: Andrew Lunn <andrew@...n.ch>
To: Vladimir Oltean <vladimir.oltean@....com>
Cc: Steven Rostedt <rostedt@...dmis.org>,
Florian Fainelli <f.fainelli@...il.com>,
Masami Hiramatsu <mhiramat@...nel.org>, netdev@...r.kernel.org,
Jakub Kicinski <kuba@...nel.org>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet <edumazet@...gle.com>,
Paolo Abeni <pabeni@...hat.com>
Subject: Re: [PATCH net-next 0/2] DSA trace events
> 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
Powered by blists - more mailing lists