From ac790a2cbb01d991d580f7c26ab3fd5c3f6f5920 Mon Sep 17 00:00:00 2001 From: fruffy Date: Tue, 9 Jul 2024 09:46:26 -0400 Subject: [PATCH] Documentation. --- docs/v1/P4Runtime-Spec.mdk | 5 +++++ docs/v1/p4runtime-id-notes.md | 1 + 2 files changed, 6 insertions(+) diff --git a/docs/v1/P4Runtime-Spec.mdk b/docs/v1/P4Runtime-Spec.mdk index d92bf33c..eddd28a9 100755 --- a/docs/v1/P4Runtime-Spec.mdk +++ b/docs/v1/P4Runtime-Spec.mdk @@ -1546,6 +1546,11 @@ control plane. This message contains the following fields: set a different default action at runtime or change the default action's arguments. +* `initial_default_action_id`, the `uint32` identifier of the default action + that is executed when the table does not match. If no explicit default + action is set, the identifier of this field will default to the id of the + `NoAction` action. + * `implementation_id`, the `uint32` identifier of the "implementation" of this table. 0 (default value) means that the table is a regular (direct) match table. Otherwise, this field will carry the ID of an extern instance specified diff --git a/docs/v1/p4runtime-id-notes.md b/docs/v1/p4runtime-id-notes.md index 282ca250..e7fab201 100644 --- a/docs/v1/p4runtime-id-notes.md +++ b/docs/v1/p4runtime-id-notes.md @@ -136,6 +136,7 @@ them may be 0, described in the notes. | Field name | Message type | Type of P4 object referred to | Notes | | ---------- | ------------ | ----------------------------- | ----- | | `const_default_action_id` | `Table` | `Action` | 0 means "the table's `default_action` is not declared `const` | +| `initial_default_action_id` | `Table` | `Action` | The initial default action used by the table. Can be overridden at runtime. | | `implementation_id` | `Table` | `ActionProfile` | 0 means "this table has no `implementation` table property. | | `direct_resource_ids` | `Table` | `DirectCounter` or `DirectMeter` | repeated so that a single table can refer to up to one of each | | `id` | sub-message `ActionRef` inside `Table` | `Action` | `ActionRef` messages are repeated, with a separate one for each action the table might invoke. `ActionRef` messages contain optional annotation and `Scope` values that are specific to how a particular table is allowed to use that `Action` |