[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aXg6zLA6Wg6nHi_R@rkannoth-OptiPlex-7090>
Date: Tue, 27 Jan 2026 09:40:52 +0530
From: Ratheesh Kannoth <rkannoth@...vell.com>
To: Jakub Kicinski <kuba@...nel.org>
CC: <netdev@...r.kernel.org>, <linux-kernel@...r.kernel.org>,
Saeed Mahameed
<saeedm@...dia.com>,
"David S. Miller" <davem@...emloft.net>,
Eric Dumazet
<edumazet@...gle.com>, Paolo Abeni <pabeni@...hat.com>,
Simon Horman
<horms@...nel.org>,
Donald Hunter <donald.hunter@...il.com>,
Jiri Pirko
<jiri@...nulli.us>, Chuck Lever <chuck.lever@...cle.com>,
"Matthieu Baerts
(NGI0)" <matttbe@...nel.org>,
Carolina Jubran <cjubran@...dia.com>
Subject: Re: [PATCH net-next v2] devlink: Implement devlink param multi
attribute nested data values
On 2026-01-27 at 06:48:59, Jakub Kicinski (kuba@...nel.org) wrote:
> On Mon, 26 Jan 2026 08:09:44 +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.
>
> Could you respin this as a series with the first driver implementing
> a param of this type? We can't merge an API without a user.
ACK. will make it part of https://patchwork.kernel.org/project/netdevbpf/list/?series=1047093 as
APIs needed by devlink are in this patch.
> --
> pw-bot: cr
Powered by blists - more mailing lists