Skip to content

Commit

Permalink
update non description
Browse files Browse the repository at this point in the history
  • Loading branch information
ved-rivos committed Jan 12, 2024
1 parent 6fbbabc commit 054a170
Show file tree
Hide file tree
Showing 2 changed files with 4 additions and 5 deletions.
4 changes: 2 additions & 2 deletions qos_bandwidth.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -161,7 +161,7 @@ all access-types, and the `AT` value is ignored.
[%header, cols="30,^10,40"]
|===
|Event ID | Encoding ^| Description
|`None` | 0 | Counter does not count and retains its value.
|`None` | 0 | Counter does not count.
|`Total Read
and Write
byte count` | 1 | Counter is incremented by the number of bytes
Expand All @@ -182,7 +182,7 @@ all access-types, and the `AT` value is ignored.
When the `EVT_ID` for a `MCID` is programmed with a non-zero and legal value,
the counter is reset to 0 and starts counting matching events for requests with
the matching `MCID` and `AT` (if `ATV` is 1). However, if the `EVT_ID` is
configured as 0, the counter retains its current value but stops counting.
configured as 0, the counter stops counting.

A controller that does not support monitoring by access-type can hardwire the
`ATV` and the `AT` fields to 0, indicating that the counter counts requests with
Expand Down
5 changes: 2 additions & 3 deletions qos_capacity.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -202,7 +202,7 @@ and the `AT` value is ignored.
[%header, cols="12,^12,70"]
|===
|Event ID | Encoding ^| Description
|`None` | 0 | Counter does not count and retains its value.
|`None` | 0 | Counter does not count.
|`Occupancy` | 1 | Counter is incremented by 1 when a request with a
matching `MCID` and `AT` allocates a unit of
capacity. The counter is decremented by 1 when a
Expand All @@ -214,8 +214,7 @@ and the `AT` value is ignored.
When the `EVT_ID` for a `MCID` is programmed with a non-zero and legal value
using the `CONFIG_EVENT` operation, the counter is reset to 0 and starts counting
matching events for requests with the matching `MCID` and `AT` (if `ATV` is 1).
However, if the `EVT_ID` is programmed to 0, the counter retains its current value
but stops counting.
However, if the `EVT_ID` is programmed to 0, the counter stops counting.

A controller that does not support monitoring by access-type can hardwire the
`ATV` and the `AT` fields to 0, indicating that the counter counts requests with
Expand Down

0 comments on commit 054a170

Please sign in to comment.