-
Notifications
You must be signed in to change notification settings - Fork 88
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Clarify section on Packet I/O messages #422
Conversation
In particular with regards to translated types.
`ControllerPacketMetadata.Metadata` message with the same `id`, in the | ||
following sense: | ||
+ If `ControllerPacketMetadata.Metadata.bitwidth` is set, or if | ||
`ControllerPacketMetadata.Metadata.type_name` is set and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As a related point, It seems like the P4RT spec doesn't have any examples of a ControllerPacketMetadata
with type_name
being utilized. Do you think it'd be valuable to add such an example and show corresponding P4NewTypeSpec
?
for the type name, then `PacketMetadata.value` must be a binary string of | ||
the specified bit width conforming to the [Bytestrings](#sec-bytestrings) | ||
requirements. | ||
+ If `ControllerPacketMetadata.Metadata.type_name` is set and |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Again, a worked-out example might help here.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. Suggest to add some more examples to illustrate some cases involving P4NewTypeSpec
I agree that adding examples would be useful. |
Sure, that's why I approved, you can put this idea in backlog. Feel free to merge. |
Sounds good. Thanks. |
In particular with regards to translated types.