Thomas Calvert

Is the architecture include file the right place for defining these methods? It seems to me like they would be better placed in an orthogonal header (e.g. `core.p4`), as there...

@jafingerhut thanks for the poke, I've just sent Mihai an email to suggest adding it to the agenda.

The spec already defines a 32-bit `FlowId_t`, which could be added to standard metadata. Currently we only have the extern `allocate_flow_id()` -- users might also wish to generate a FlowId...

I think the first 2 lines of each file should be swapped to fix the build. Otherwise LGTM. 👍

How about "offload engine" ?

> If a program is written by a developer assuming architecture (a), is it straightforward for a compiler to take that source code and compile it to a hardware target...

> Note: It doesn't seem like a P4 compiler would need to be very sophisticated to notice that the first 17 statements of an action like the example above do...

I would also suggest 3 inout structures, one for each parser/control/deparser. From a mechanics point of view, would we expect cross-platform PNA code to look something like: ``` #include #ifdef...

Text changed as suggested, and forward reference added.

If PNA supports mutable table entries that is also a mechanism for storing state in-between passes. Various implementations will have different cost functions for preserving context in: metadata vs packet...