[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20240306183351.4ebcbfdf@gandalf.local.home>
Date: Wed, 6 Mar 2024 18:33:51 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Tobias Waldekranz <tobias@...dekranz.com>
Cc: Paolo Abeni <pabeni@...hat.com>, davem@...emloft.net, kuba@...nel.org,
roopa@...dia.com, razor@...ckwall.org, bridge@...ts.linux.dev,
netdev@...r.kernel.org, jiri@...nulli.us, ivecera@...hat.com,
mhiramat@...nel.org, linux-trace-kernel@...r.kernel.org
Subject: Re: [PATCH v3 net-next 4/4] net: switchdev: Add tracepoints
On Wed, 06 Mar 2024 23:45:57 +0100
Tobias Waldekranz <tobias@...dekranz.com> wrote:
> > How big is this info?
>
> The common struct (switchdev_notifier_info) is 24B at the
> moment. Depending on __entry->val, the size of the enclosing
> notification (e.g. switchdev_notifier_port_obj_info) is between
> 40-64B. This pattern may then repeat again inside the concrete notifier,
> where you have a pointer to a common object (e.g. switchdev_obj, 48B)
> whose outer size (e.g. switchdev_obj_port_vlan, 56B) is determined by an
> accompanying enum.
As long as it's under 1K, you should be good.
-- Steve
Powered by blists - more mailing lists