[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <ZM01ezEkJw4D27Xl@nanopsycho>
Date: Fri, 4 Aug 2023 19:29:31 +0200
From: Jiri Pirko <jiri@...nulli.us>
To: kuba@...nel.org
Cc: netdev@...r.kernel.org
Subject: ynl - mutiple policies for one nested attr used in multiple cmds
Hi Kuba.
I need to have one nested attribute but according to what cmd it is used
with, there will be different nested policy.
If I'm looking at the codes correctly, that is not currenly supported,
correct?
If not, why idea how to format this in yaml file?
Pehaps something like:
-
name: dump-selector
type: nest
nested-attributes: dl-dump-selector
-
name: dl-dev-dump-selector
subset-of: devlink
attributes:
-
name: bus-name
type: string
-
name: dev-name
type: string
-
name: dl-port-dump-selector
subset-of: devlink
attributes:
-
name: bus-name
type: string
-
name: dev-name
type: string
-
name: port-index
type: u32
And then:
dump:
pre: devlink-nl-start
post: devlink-nl-done
request:
attributes:
- dump-selector@...dev-dump-selector
...
dump:
pre: devlink-nl-start
post: devlink-nl-done
request:
attributes:
- dump-selector@...port-dump-selector
Idk, looks a bit odd though to parse the attr strings.
Any idea?
Powered by blists - more mailing lists