... | ... | @@ -268,7 +268,7 @@ Then we can call digest in the ingress pipeline: |
|
|
digest(1, meta.digest_data); //assume that metadata is called meta in the ingress parameters
|
|
|
```
|
|
|
|
|
|
> Note that the first parameter of digest is always 1.
|
|
|
> Note that the first parameter of digest is always `1`.
|
|
|
|
|
|
Receiving digested packets is not trivial, since the switch adds some control header that needs to be parsed, furthermore, for each digested packet, the switch expects an acknowledgement message (used to filter duplicates).
|
|
|
|
... | ... | |