From: Przemek Kitszel <przemyslaw.kitszel@intel.com>
To: Ratheesh Kannoth <rkannoth@marvell.com>,
<intel-wired-lan@lists.osuosl.org>, <netdev@vger.kernel.org>
Cc: <akiyano@amazon.com>, <andrew+netdev@lunn.ch>,
<anthony.l.nguyen@intel.com>, <arkadiusz.kubalewski@intel.com>,
<brett.creeley@amd.com>, <darinzon@amazon.com>,
<davem@davemloft.net>, <donald.hunter@gmail.com>,
<edumazet@google.com>, <linux-rdma@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <horms@kernel.org>,
<idosch@nvidia.com>, <ivecera@redhat.com>, <jiri@resnulli.us>,
<kuba@kernel.org>, <leon@kernel.org>, <mbloch@nvidia.com>,
<michael.chan@broadcom.com>, <pabeni@redhat.com>,
<pavan.chebbi@broadcom.com>, <petrm@nvidia.com>,
<Prathosh.Satish@microchip.com>, <saeedm@nvidia.com>,
<sgoutham@marvell.com>, <tariqt@nvidia.com>,
<vadim.fedorenko@linux.dev>, <oss-drivers@corigine.com>
Subject: Re: [PATCH v12 net-next 3/9] devlink: pass param values by pointer
Date: Mon, 11 May 2026 15:39:59 +0200 [thread overview]
Message-ID: <a998b2f9-278b-4bed-b050-d292ed4c8c64@intel.com> (raw)
In-Reply-To: <20260508034912.4082520-4-rkannoth@marvell.com>
On 5/8/26 05:49, Ratheesh Kannoth wrote:
> union devlink_param_value grows substantially once U64 array
> parameters are added to devlink (from 32 bytes to over 264 bytes).
> devlink_nl_param_value_fill_one() and devlink_nl_param_value_put()
> copy the union by value in several places. Passing two instances as
> value arguments alone consumes over 528 bytes of stack; combined with
> deeper call chains the parameter stack can approach 800 bytes and trip
> CONFIG_FRAME_WARN more easily.
>
> Switch internal helpers and exported driver APIs to pass pointers to
> union devlink_param_value rather than passing the union by value.
>
> Signed-off-by: Ratheesh Kannoth <rkannoth@marvell.com>
> ---
> drivers/dpll/zl3073x/devlink.c | 6 +-
> drivers/net/ethernet/amazon/ena/ena_devlink.c | 8 +--
> drivers/net/ethernet/amd/pds_core/core.h | 2 +-
> drivers/net/ethernet/amd/pds_core/devlink.c | 2 +-
> .../net/ethernet/broadcom/bnxt/bnxt_devlink.c | 6 +-
> .../net/ethernet/intel/ice/devlink/devlink.c | 30 ++++----
those are pure mechanical changes, no problem for me
Acked-by: Przemek Kitszel <przemyslaw.kitszel@intel.com>
> .../marvell/octeontx2/af/rvu_devlink.c | 22 +++---
> .../marvell/octeontx2/nic/otx2_devlink.c | 4 +-
> drivers/net/ethernet/mellanox/mlx4/main.c | 14 ++--
> .../net/ethernet/mellanox/mlx5/core/devlink.c | 72 +++++++++----------
> .../mellanox/mlx5/core/eswitch_offloads.c | 2 +-
> .../net/ethernet/mellanox/mlx5/core/fs_core.c | 4 +-
> .../mellanox/mlx5/core/lib/nv_param.c | 12 ++--
> drivers/net/ethernet/mellanox/mlxsw/core.c | 8 +--
> .../ethernet/netronome/nfp/devlink_param.c | 6 +-
> drivers/net/netdevsim/dev.c | 4 +-
> include/net/devlink.h | 4 +-
> net/devlink/param.c | 32 ++++-----
> 18 files changed, 119 insertions(+), 119 deletions(-)
>
next prev parent reply other threads:[~2026-05-11 13:40 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 3:49 [PATCH v12 net-next 0/9] octeontx2-af: npc: Enhancements Ratheesh Kannoth
2026-05-08 3:49 ` [PATCH v12 net-next 1/9] octeontx2-af: npc: cn20k: debugfs enhancements Ratheesh Kannoth
2026-05-11 2:25 ` Ratheesh Kannoth
2026-05-08 3:49 ` [PATCH v12 net-next 2/9] net/mlx5e: trim stack use in PCIe congestion threshold helper Ratheesh Kannoth
2026-05-08 9:02 ` David Laight
2026-05-08 3:49 ` [PATCH v12 net-next 3/9] devlink: pass param values by pointer Ratheesh Kannoth
2026-05-11 13:39 ` Przemek Kitszel [this message]
2026-05-08 3:49 ` [PATCH v12 net-next 4/9] devlink: Implement devlink param multi attribute nested data values Ratheesh Kannoth
2026-05-11 2:31 ` Ratheesh Kannoth
2026-05-08 3:49 ` [PATCH v12 net-next 5/9] octeontx2-af: npc: cn20k: add subbank search order control Ratheesh Kannoth
2026-05-11 2:32 ` Ratheesh Kannoth
2026-05-08 3:49 ` [PATCH v12 net-next 6/9] octeontx2: cn20k: Coordinate default rules with NIX LF lifecycle Ratheesh Kannoth
2026-05-11 2:44 ` Ratheesh Kannoth
2026-05-08 3:49 ` [PATCH v12 net-next 7/9] octeontx2-af: npc: Support for custom KPU profile from filesystem Ratheesh Kannoth
2026-05-11 3:23 ` Ratheesh Kannoth
2026-05-11 3:27 ` Ratheesh Kannoth
2026-05-11 11:55 ` [Intel-wired-lan] " Loktionov, Aleksandr
2026-05-08 3:49 ` [PATCH v12 net-next 8/9] octeontx2: cn20k: Respect NPC MCAM X2/X4 profile in flows and DFT alloc Ratheesh Kannoth
2026-05-11 3:25 ` Ratheesh Kannoth
2026-05-08 3:49 ` [PATCH v12 net-next 9/9] octeontx2-af: npc: cn20k: Allocate npc_priv and dstats dynamically Ratheesh Kannoth
2026-05-11 3:26 ` Ratheesh Kannoth
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=a998b2f9-278b-4bed-b050-d292ed4c8c64@intel.com \
--to=przemyslaw.kitszel@intel.com \
--cc=Prathosh.Satish@microchip.com \
--cc=akiyano@amazon.com \
--cc=andrew+netdev@lunn.ch \
--cc=anthony.l.nguyen@intel.com \
--cc=arkadiusz.kubalewski@intel.com \
--cc=brett.creeley@amd.com \
--cc=darinzon@amazon.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=idosch@nvidia.com \
--cc=intel-wired-lan@lists.osuosl.org \
--cc=ivecera@redhat.com \
--cc=jiri@resnulli.us \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=michael.chan@broadcom.com \
--cc=netdev@vger.kernel.org \
--cc=oss-drivers@corigine.com \
--cc=pabeni@redhat.com \
--cc=pavan.chebbi@broadcom.com \
--cc=petrm@nvidia.com \
--cc=rkannoth@marvell.com \
--cc=saeedm@nvidia.com \
--cc=sgoutham@marvell.com \
--cc=tariqt@nvidia.com \
--cc=vadim.fedorenko@linux.dev \
/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