Scheduler group parent node as port about sai HOT 10 OPEN

from sai.

So my understanding is that we do not have to specify SAI_SCHEDULER_GROUP_ATTR_PARENT_NODE for the level 0 ?

from sai.

from sai.

So then it is not needed to have SAI_OBJECT_TYPE_PORT in @objects section ? Or it is needed to handle
multiple cases:

1) level=0, parent_node=port
2) level=0, parent_node is not specified, so the port from the "port" attribute is used

?

from sai.

@lguohan Would you please give some clarification on this ? As it is till not clear for me.

Thanks,

from sai.

it seems redundant, you can add metadata conditional on level > 0 to make this attribute conditional. and then remove the SAI_OBJECT_TYPE_QUEUE

from sai.

thanks, but you meant to remove SAI_OBJECT_TYPE_PORT ?

from sai.

currently condition operator supports only "==" but there is a plan do add other operators, but this will complacate comparison logic logic,
you can live in description proper condition restriction, and for now if you want force it you can and each condition as " level == 1 or level == 2 or level == 3" how many levels we can have right now ? 8? 16?

from sai.

anywy, i already saw on other vendors implementation that level 0 is implemented correctly anyway pointing to port

from sai.

sorry for the typo, yes, remove SAI_OBJECT_TYPE_PORT

from sai.