[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20240812082544.277b594d@kernel.org>
Date: Mon, 12 Aug 2024 08:25:44 -0700
From: Jakub Kicinski <kuba@...nel.org>
To: Paolo Abeni <pabeni@...hat.com>
Cc: Jiri Pirko <jiri@...nulli.us>, Donald Hunter <donald.hunter@...il.com>,
netdev@...r.kernel.org, Madhu Chittim <madhu.chittim@...el.com>, Sridhar
Samudrala <sridhar.samudrala@...el.com>, Simon Horman <horms@...nel.org>,
John Fastabend <john.fastabend@...il.com>, Sunil Kovvuri Goutham
<sgoutham@...vell.com>, Jamal Hadi Salim <jhs@...atatu.com>
Subject: Re: [PATCH v3 02/12] netlink: spec: add shaper YAML spec
On Mon, 12 Aug 2024 16:58:33 +0200 Paolo Abeni wrote:
> > It's a tree, so perhaps just stick with tree terminology, everyone is
> > used to that. Makes sense? One way or another, this needs to be
> > properly described in docs, all terminology. That would make things more
> > clear, I believe.
>
> @Jakub, would you be ok with:
>
> 'inputs' -> 'leaves'
> 'output' -> 'node'
> ?
I think the confusion is primarily about the parent / child.
input and output should be very clear, IMO.
> Also while at it, I think renaming the 'group()' operation as
> 'node_set()' could be clearer (or at least less unclear), WDYT?
No idea how we arrived at node_set(), and how it can possibly
represent a grouping operation.
The operations is grouping inputs and creating a scheduler node.
> Note: I think it's would be more user-friendly to keep a single
> delete/get/dump operation for 'nodes' and leaves.
Are you implying that nodes and leaves are different types of objects?
Aren't leaves nodes without any inputs?
Powered by blists - more mailing lists