Attendees: Rajshekhar B. (Arista), Ramesh S. (Cisco), Mukesh H. (VMware), Jonathan S. (Intel, Deep Insight), Mickey S. (Intel, Barefoot), JK L. (Intel, E2E App).
Three topics were discussed today.
It has two enums, one for ingress and the other for egress. Around 100 reasons in total.
It assumes a 32b or larger field to carry the reason code. INT and Report spec has 8 bits.
AIs:
For INT standard instructions, the INT spec will continue to define the bitmap for the set of standard metadata.
Each domain can do the same for domain-specific instruction.
AI:
The WG agreed for the spec to recommend static UDP src port number by default, while allowing entropy or randomization in case the collector infra can handle varying UDP src port number. For example, some NICs can be configured to ignore UDP src port in RSS hash inputs.
AI:
Meanwhile, there is a progress in hosting P4 open-source projects under P4.org. We will share updates via email or in the next WG meeting.
Thanks,
JK
Mukesh
Hi Team,
Please find below attached the proposal for P4 drop reason codes. Feel free
to add/delete/modify the list.
https://docs.google.com/document/d/1u-9ra4fL592MEzxJHD_z9uSLZfoBT5mIaoCy5rWIglg/edit?usp=sharing
Drop reasons are divided into 6 categories:
L2 reasons
2.
L3 reasons
3.
Tunnel reasons
4.
Policy reasons
5.
Congestion related reasons
6.
Vendor specific reasons
Reason codes will be allotted once the drop reasons are finalized.
Let me know if you have any questions.
On Wed, Jan 13, 2021 at 6:59 AM Lee, Jeongkeun jk.lee@intel.com wrote:
Attendees: Rajshekhar B. (Arista), Ramesh S. (Cisco), Mukesh H. (VMware),
Jonathan S. (Intel, Deep Insight), Mickey S. (Intel, Barefoot), JK L.
(Intel, E2E App).
Three topics were discussed today.
It has two enums, one for ingress and the other for egress. Around 100
reasons in total.
It assumes a 32b or larger field to carry the reason code. INT and Report
spec has 8 bits.
AIs:
For INT standard instructions, the INT spec will continue to define the
bitmap for the set of standard metadata.
Each domain can do the same for domain-specific instruction.
AI:
The WG agreed for the spec to recommend static UDP src port number by
default, while allowing entropy or randomization in case the collector
infra can handle varying UDP src port number. For example, some NICs can be
configured to ignore UDP src port in RSS hash inputs.
AI:
Meanwhile, there is a progress in hosting P4 open-source projects under
P4.org. We will share updates via email or in the next WG meeting.
Thanks,
JK
Mukesh
P4-apps mailing list
P4-apps@lists.p4.org
http://lists.p4.org/mailman/listinfo/p4-apps_lists.p4.org
--
Thanks,
Raj