Support for Router Interface Meta Data#2209
Support for Router Interface Meta Data#2209komal-marvell wants to merge 1 commit intoopencomputeproject:masterfrom
Conversation
doc/SAI-Proposal-RIF-Metadata.md
Outdated
| typedef union _sai_acl_capability_extended_value_t | ||
| { | ||
| /** @validonly type == SAI_ACL_CAPABILITY_EXTENDED_TYPE_ROUTER_INTERFACE_META_DATA */ | ||
| sai_u32_range_t router_interface_meta_data_range; |
There was a problem hiding this comment.
what happens if we want to add additional attributes in the future and need a bigger data type. This becomes again non binary compatible
There was a problem hiding this comment.
so this is a new complex mechanism, but seems not extendable
and in the end, do you really need different metadata range per stage ?
or can we just add new attribute like SAI_SWITCH_ATTR_ACL_USER_META_DATA_RANGE
komal-marvell
force-pushed
the
rif_meta
branch
2 times, most recently
from
f1236f4 to
9e7d9da
Compare
Signed-off-by: Komal Shah <kshah2@marvell.com>
komal-marvell
force-pushed
the
rif_meta
branch
from
9e7d9da to
6c9a192
Compare
|
@komal-marvell - could you please resolve branch conflicts and update the PR with the usecase as discussed in the last meeting? |
|
@komal-marvell - gentle reminder on this |
|
@rck-innovium, @rajkumar38, @komal-marvell - reminder on this |
|
@rck-innovium, @rajkumar38 - following up on this. Are we able to update the branch and resovle conflicts? |
3 participants
Metadata can be assigned on Router Interface and subsequently matched in ACL entries, providing increased flexibility for policy management.