From: Jakub Kicinski <kuba@kernel.org>
To: Ratheesh Kannoth <rkannoth@marvell.com>
Cc: <netdev@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<sgoutham@marvell.com>, <davem@davemloft.net>,
<edumazet@google.com>, <pabeni@redhat.com>, <horms@kernel.org>,
<donald.hunter@gmail.com>, <jiri@resnulli.us>,
<chuck.lever@oracle.com>, <matttbe@kernel.org>,
<cjubran@nvidia.com>, <shshitrit@nvidia.com>,
"Saeed Mahameed" <saeedm@nvidia.com>
Subject: Re: [PATCH v5 net-next 2/5] devlink: Implement devlink param multi attribute nested data values
Date: Wed, 18 Mar 2026 19:57:48 -0700 [thread overview]
Message-ID: <20260318195748.6754aafc@kernel.org> (raw)
In-Reply-To: <20260317045623.250187-3-rkannoth@marvell.com>
On Tue, 17 Mar 2026 10:26:20 +0530 Ratheesh Kannoth wrote:
> Devlink param value attribute is not defined since devlink is handling
> the value validating and parsing internally, this allows us to implement
> multi attribute values without breaking any policies.
>
> Devlink param multi-attribute values are considered to be dynamically
> sized arrays of u32 values, by introducing a new devlink param type
> DEVLINK_PARAM_TYPE_U32_ARRAY, driver and user space can set a variable
> count of u32 values into the DEVLINK_ATTR_PARAM_VALUE_DATA attribute.
>
> Implement get/set parsing and add to the internal value structure passed
> to drivers.
>
> This is useful for devices that need to configure a list of values for
> a specific configuration.
Jiri's suggesting to use uint seems quite sensible. That way we don't
have to add another type if anyone needs >32b in the future. Should
be a fairly straightforward conversion. All the real types in the
kernel s/u32/u64/ and the netlink helper and API s/u32/uint/
next prev parent reply other threads:[~2026-03-19 2:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-17 4:56 [PATCH v5 net-next 0/5] octeontx2-af: npc: Enhancements Ratheesh Kannoth
2026-03-17 4:56 ` [PATCH v5 net-next 1/5] octeontx2-af: npc: cn20k: debugfs enhancements Ratheesh Kannoth
2026-03-17 4:56 ` [PATCH v5 net-next 2/5] devlink: Implement devlink param multi attribute nested data values Ratheesh Kannoth
2026-03-19 2:57 ` Jakub Kicinski [this message]
2026-03-17 4:56 ` [PATCH v5 net-next 3/5] octeontx2-af: npc: cn20k: add subbank search order control Ratheesh Kannoth
2026-03-17 4:56 ` [PATCH v5 net-next 4/5] octeontx2-af: npc: cn20k: dynamically allocate and free default MCAM entries Ratheesh Kannoth
2026-03-17 4:56 ` [PATCH v5 net-next 5/5] octeontx2-af: npc: Support for custom KPU profile from filesystem 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=20260318195748.6754aafc@kernel.org \
--to=kuba@kernel.org \
--cc=chuck.lever@oracle.com \
--cc=cjubran@nvidia.com \
--cc=davem@davemloft.net \
--cc=donald.hunter@gmail.com \
--cc=edumazet@google.com \
--cc=horms@kernel.org \
--cc=jiri@resnulli.us \
--cc=linux-kernel@vger.kernel.org \
--cc=matttbe@kernel.org \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=rkannoth@marvell.com \
--cc=saeedm@nvidia.com \
--cc=sgoutham@marvell.com \
--cc=shshitrit@nvidia.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.