Re: [patch net-next RFC 02/12] devlink: extend attrs_set for setting port flavours

2018-03-22 Thread Jiri Pirko
Fri, Mar 23, 2018 at 04:36:24AM CET, jakub.kicin...@netronome.com wrote: >On Thu, 22 Mar 2018 11:55:12 +0100, Jiri Pirko wrote: >> enum devlink_attr { >> /* don't change the order or add anything between, this is ABI! */ >> DEVLINK_ATTR_UNSPEC, >> @@ -224,6 +242,7 @@ enum devlink_attr {

Re: [patch net-next RFC 02/12] devlink: extend attrs_set for setting port flavours

2018-03-22 Thread Jakub Kicinski
On Thu, 22 Mar 2018 11:55:12 +0100, Jiri Pirko wrote: > enum devlink_attr { > /* don't change the order or add anything between, this is ABI! */ > DEVLINK_ATTR_UNSPEC, > @@ -224,6 +242,7 @@ enum devlink_attr { > DEVLINK_ATTR_DPIPE_TABLE_RESOURCE_ID, /* u64 */ > DEVLINK_AT

[patch net-next RFC 02/12] devlink: extend attrs_set for setting port flavours

2018-03-22 Thread Jiri Pirko
From: Jiri Pirko Devlink ports can have specific flavour according to the purpose of use. This patch extend attrs_set so the driver can say which flavour port has. Initial flavours are: physical, pf_rep, vf_rep, cpu, dsa User can query this to see right away what is the purpose of each port. Sig