fyb/p4tutorials-turkce
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

readme: Update logs path (#448)

Browse Source 
* readme: remove trailing whitespaces

Signed-off-by: Radostin Stoyanov <rstoyanov@fedoraproject.org>

* readme: update path to log files

Fixes: #447

Signed-off-by: Radostin Stoyanov <rstoyanov@fedoraproject.org>
This commit is contained in:
Radostin Stoyanov
2022-01-19 17:59:20 +00:00
committed by GitHub
parent 1fc826aa43
commit ccc5693807
9 changed files with 42 additions and 42 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
exercises/link_monitor/README.md
View File

@@ -11,7 +11,7 @@ packet such that it is able to pick up the egress link utilization
at each hop and deliver it to a host for monitoring purposes.
Our probe packet will contain the following three header types:
```
```
// Top-level probe header, indicates how many hops this probe
// packet has traversed so far.
header probe_t {
@@ -46,7 +46,7 @@ two register arrays:
* `byte_cnt_reg` - counts the number of bytes transmitted out of
each port since the last probe packet was transmitted out of
the port.
* `last_time_reg` - stores the last time that a probe packet was
* `last_time_reg` - stores the last time that a probe packet was
transmitted out of each port.
Our P4 program will be written for the V1Model architecture implemented
@@ -69,7 +69,7 @@ extend this skeleton program to fill out the fields in the probe
packet.
Before that, let's compile and test the incomplete `link_monitor.p4`
program:
program:
1. In your shell, run:
```bash
@@ -95,7 +95,7 @@ path indicated in link-monitor-topo.png.
```
4. In the other terminal run the `receive.py` script to start
receiving and parsing the probe packets. This allows us to monitor
the link utilization within the network.
the link utilization within the network.
```bash
./receive.py
```