[P4-dev] P4-16, D2. in Open Issues
mbudiu at vmware.com
Tue May 2 21:35:39 EDT 2017
P4-16 has no operations to modify tables from the data-plane, and neither does P4-14.
A specific P4-16 architecture could provide an extern function for this purpose, but the P4 standard architecture draft under development has no such function.
Registers can be used for bi-directional communication between the control-plane and the data-plane; they will probably be part of the standard architecture.
From: P4-dev [mailto:p4-dev-bounces at lists.p4.org] On Behalf Of hemant at mnkcg.com
Sent: Tuesday, May 2, 2017 6:17 PM
To: 'p4-dev' <p4-dev at lists.p4.org>
Subject: [P4-dev] P4-16, D2. in Open Issues
A table residing in the data plane has to be also writeable – can’t be just read-only. Congestion control algorithms in the data plane of a switch use a table for read and write operations. To help debugs issues in the data plane, it makes sense to have the tables be also accessible by the control plane. As for API, I prefer a compiler functions – let the compiler do all this fun work.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the P4-dev