readme: Update logs path (#448)
* 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:
committed by
GitHub
parent
1fc826aa43
commit
ccc5693807
@@ -78,7 +78,7 @@ missing piece.
|
||||
First we have to change the ipv4_t header by splitting the TOS field
|
||||
into DiffServ and ECN fields. Remember to update the checksum block
|
||||
accordingly. Then, in the egress control block we must compare the
|
||||
protocol in IP header with IP protocols. Based on the traffic classes
|
||||
protocol in IP header with IP protocols. Based on the traffic classes
|
||||
and priority, the `diffserv` flag will be set.
|
||||
|
||||
A complete `qos.p4` will contain the following components:
|
||||
@@ -102,7 +102,7 @@ A complete `qos.p4` will contain the following components:
|
||||
|
||||
Follow the instructions from Step 1. This time, when your message from
|
||||
`h1` is delivered to `h2`, you should see `tos` values change from 0x1
|
||||
to 0xb9 for UDP and 0xb1 for TCP. It depends upon the action you choose
|
||||
to 0xb9 for UDP and 0xb1 for TCP. It depends upon the action you choose
|
||||
in Ingress processing.
|
||||
|
||||
To easily track the `tos` values you may want to redirect the output
|
||||
@@ -148,7 +148,7 @@ There are several ways that problems might manifest:
|
||||
implementation.
|
||||
3. `qos.p4` compiles, and the control plane rules are installed, but
|
||||
the switch does not process packets in the desired way. The
|
||||
`/tmp/p4s.<switch-name>.log` files contain trace messages
|
||||
`logs/sX.log` files contain trace messages
|
||||
describing how each switch processes each packet. The output is
|
||||
detailed and can help pinpoint logic errors in your implementation.
|
||||
The `build/<switch-name>-<interface-name>.pcap` also contains the
|
||||
|
||||
Reference in New Issue
Block a user