[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <m2ed6sl52j.fsf@gmail.com>
Date: Tue, 13 Aug 2024 18:12:52 +0100
From: Donald Hunter <donald.hunter@...il.com>
To: Jakub Kicinski <kuba@...nel.org>
Cc: Paolo Abeni <pabeni@...hat.com>, Jiri Pirko <jiri@...nulli.us>,
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
Jakub Kicinski <kuba@...nel.org> writes:
> 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.
input / output seems the most intuitive of the different terms that have
been suggested.
Powered by blists - more mailing lists