All of lore.kernel.org
 help / color / mirror / Atom feed
From: Saeed Mahameed <saeed@kernel.org>
To: stephen@networkplumber.org, dsahern@gmail.com,
	Jiri Pirko <jiri@nvidia.com>,
	jiri@resnulli.us
Cc: netdev@vger.kernel.org, Saeed Mahameed <saeedm@nvidia.com>
Subject: [PATCH iproute2 00/10] devlink params nested multi-attribute values
Date: Thu, 27 Feb 2025 18:18:27 -0800	[thread overview]
Message-ID: <20250228021837.880041-1-saeed@kernel.org> (raw)

From: Saeed Mahameed <saeedm@nvidia.com>

This patch series reworks devlink parameters and introduces support for nested
value attributes. It also adds support for showing and setting port parameters
with multi-attribute value data.

example:
     $ devlink dev param show pci/... name multi-value-param
        name multi-value-param type driver-specific
        values:
          cmode permanent value: 0,1,2,3,4,5,6,7

     $ devlink dev param set pci/... name multi-value-param \
            value 4,5,6,7,0,1,2,3 cmode permanent

This series is based on the following devlink kernel patches:
https://lore.kernel.org/netdev/20250228021227.871993-1-saeed@kernel.org/

Thanks,
Saeed

Jiri Pirko (2):
  update kernel headers
  devlink: use dynamic attributes enum

Saeed Mahameed (8):
  devlink: param show: handle multi-attribute values
  devlink: param set: reuse cmd_dev_param_set_cb for port params set
  devlink: rename param_ctx to dl_param
  devlink: helper function to read user param input into dl_param
  devlink: helper function to compare dl_params
  devlink: helper function to put param value mnl attributes from
    dl_params
  devlink: helper function to parse param vlaue attributes into dl_param
  devlink: params set: add support for nested attributes values

 devlink/devlink.c            | 689 ++++++++++++++++++++---------------
 include/uapi/linux/devlink.h |  18 +
 2 files changed, 422 insertions(+), 285 deletions(-)

-- 
2.48.1


             reply	other threads:[~2025-02-28  2:18 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-28  2:18 Saeed Mahameed [this message]
2025-02-28  2:18 ` [PATCH iproute2 01/10] update kernel headers Saeed Mahameed
2025-02-28  2:18 ` [PATCH iproute2 02/10] devlink: use dynamic attributes enum Saeed Mahameed
2025-02-28  2:18 ` [PATCH iproute2 03/10] devlink: param show: handle multi-attribute values Saeed Mahameed
2025-02-28  2:18 ` [PATCH iproute2 04/10] devlink: param set: reuse cmd_dev_param_set_cb for port params set Saeed Mahameed
2025-02-28  2:18 ` [PATCH iproute2 05/10] devlink: rename param_ctx to dl_param Saeed Mahameed
2025-02-28  2:18 ` [PATCH iproute2 06/10] devlink: helper function to read user param input into dl_param Saeed Mahameed
2025-02-28  2:18 ` [PATCH iproute2 07/10] devlink: helper function to compare dl_params Saeed Mahameed
2025-02-28  2:18 ` [PATCH iproute2 08/10] devlink: helper function to put param value mnl attributes from dl_params Saeed Mahameed
2025-02-28  2:18 ` [PATCH iproute2 09/10] devlink: helper function to parse param vlaue attributes into dl_param Saeed Mahameed
2025-02-28  2:18 ` [PATCH iproute2 10/10] devlink: params set: add support for nested attributes values Saeed Mahameed

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=20250228021837.880041-1-saeed@kernel.org \
    --to=saeed@kernel.org \
    --cc=dsahern@gmail.com \
    --cc=jiri@nvidia.com \
    --cc=jiri@resnulli.us \
    --cc=netdev@vger.kernel.org \
    --cc=saeedm@nvidia.com \
    --cc=stephen@networkplumber.org \
    /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.