netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jakub Kicinski <kuba@kernel.org>
To: Paolo Abeni <pabeni@redhat.com>
Cc: netdev@vger.kernel.org, Jiri Pirko <jiri@resnulli.us>,
	Madhu Chittim <madhu.chittim@intel.com>,
	Sridhar Samudrala <sridhar.samudrala@intel.com>,
	Simon Horman <horms@kernel.org>,
	John Fastabend <john.fastabend@gmail.com>,
	Sunil Kovvuri Goutham <sgoutham@marvell.com>,
	Jamal Hadi Salim <jhs@mojatatu.com>,
	Donald Hunter <donald.hunter@gmail.com>,
	anthony.l.nguyen@intel.com, przemyslaw.kitszel@intel.com,
	intel-wired-lan@lists.osuosl.org, edumazet@google.com,
	Stanislav Fomichev <stfomichev@gmail.com>
Subject: Re: [PATCH v8 net-next 02/15] netlink: spec: add shaper YAML spec
Date: Tue, 8 Oct 2024 17:14:05 -0700	[thread overview]
Message-ID: <20241008171405.42e8890e@kernel.org> (raw)
In-Reply-To: <72241d8f846c67b7201f0293956ef6db6bbbf176.1727704215.git.pabeni@redhat.com>

On Mon, 30 Sep 2024 15:53:49 +0200 Paolo Abeni wrote:
> +      name: group
> +      doc: |
> +        Create or update a scheduling group, attaching the specified
> +        @leaves shapers under the specified node identified by @handle,
> +        creating the latter, if needed.

This line is unnecessary? The first line already says "create or update"
so no need to say again that the node will be created?

> +        The @leaves shapers scope must be @queue and the node shaper
> +        scope must be either @node or @netdev.
> +        When the node shaper has @node scope, if the @handle @id is not
> +        specified, a new shaper of such scope is created, otherwise the
> +        specified node must already exist.

> +        The @parent handle for the node shaper is optional in most cases.
> +        For newly created node scope shaper, the node parent is set by
> +        default to the parent linked to the @leaves before the @group
> +        operation. If, prior to the grouping operation, the @leaves
> +        have different parents, the node shaper @parent must be explicitly
> +        set.

How about:

	The @parent handle for a new node shaper defaults to the parent
	of all the leaves, provided all the leaves share the same parent.
	Otherwise @parent handle must be specified.

> +        The user can optionally provide shaping attributes for the node
> +        shaper.
> +        The operation is atomic, on failure no change is applied to
> +        the device shaping configuration, otherwise the @node shaper
> +        full identifier, comprising @binding and @handle, is provided
> +        as the reply.

We should also mention that if the node already exists the group
operation will _add_ leaves to it, rather than recreating it with
the provided set of leaves. Right? My intuition was that the node
will get the specified set of leaves and the other leaves get deleted.
The current behavior is fine, but needs to be documented.

  reply	other threads:[~2024-10-09  0:14 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-30 13:53 [PATCH v8 net-next 00/15] net: introduce TX H/W shaping API Paolo Abeni
2024-09-30 13:53 ` [PATCH v8 net-next 01/15] genetlink: extend info user-storage to match NL cb ctx Paolo Abeni
2024-09-30 13:53 ` [PATCH v8 net-next 02/15] netlink: spec: add shaper YAML spec Paolo Abeni
2024-10-09  0:14   ` Jakub Kicinski [this message]
2024-09-30 13:53 ` [PATCH v8 net-next 03/15] net-shapers: implement NL get operation Paolo Abeni
2024-09-30 13:53 ` [PATCH v8 net-next 04/15] net-shapers: implement NL set and delete operations Paolo Abeni
2024-09-30 13:53 ` [PATCH v8 net-next 05/15] net-shapers: implement NL group operation Paolo Abeni
2024-09-30 13:53 ` [PATCH v8 net-next 06/15] net-shapers: implement delete support for NODE scope shaper Paolo Abeni
2024-09-30 13:53 ` [PATCH v8 net-next 07/15] net-shapers: implement shaper cleanup on queue deletion Paolo Abeni
2024-10-08 23:51   ` Jakub Kicinski
2024-09-30 13:53 ` [PATCH v8 net-next 08/15] netlink: spec: add shaper introspection support Paolo Abeni
2024-10-08 23:50   ` Jakub Kicinski
2024-09-30 13:53 ` [PATCH v8 net-next 09/15] net: shaper: implement " Paolo Abeni
2024-10-08 23:48   ` Jakub Kicinski
2024-09-30 13:53 ` [PATCH v8 net-next 10/15] net-shapers: implement cap validation in the core Paolo Abeni
2024-09-30 13:53 ` [PATCH v8 net-next 11/15] testing: net-drv: add basic shaper test Paolo Abeni
2024-09-30 13:53 ` [PATCH v8 net-next 12/15] virtchnl: support queue rate limit and quanta size configuration Paolo Abeni
2024-09-30 13:54 ` [PATCH v8 net-next 13/15] ice: Support VF " Paolo Abeni
2024-09-30 13:54 ` [PATCH v8 net-next 14/15] iavf: Add net_shaper_ops support Paolo Abeni
2024-09-30 13:54 ` [PATCH v8 net-next 15/15] iavf: add support to exchange qos capabilities Paolo Abeni
2024-10-07 15:20 ` [PATCH v8 net-next 00/15] net: introduce TX H/W shaping API Jiri Pirko
2024-10-08 23:21 ` Jakub Kicinski

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=20241008171405.42e8890e@kernel.org \
    --to=kuba@kernel.org \
    --cc=anthony.l.nguyen@intel.com \
    --cc=donald.hunter@gmail.com \
    --cc=edumazet@google.com \
    --cc=horms@kernel.org \
    --cc=intel-wired-lan@lists.osuosl.org \
    --cc=jhs@mojatatu.com \
    --cc=jiri@resnulli.us \
    --cc=john.fastabend@gmail.com \
    --cc=madhu.chittim@intel.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=sgoutham@marvell.com \
    --cc=sridhar.samudrala@intel.com \
    --cc=stfomichev@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).