Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

allow option to configure zero capacity blocks #24

Merged
merged 2 commits into from
Feb 26, 2024
Merged

allow option to configure zero capacity blocks #24

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
605d8d4
allow option to configure zero capacity blocks
ved-rivos Feb 13, 2024
b8090ee
fix typo
ved-rivos Feb 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion qos_bandwidth.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -428,7 +428,7 @@ When the `Mweight` parameter is not set to 0, the amount of unused bandwidth
allocated to `RCID=x` during contention with another `RCID` that is also
permitted to use unused bandwidth is determined by dividing the `Mweight` of
`RCID=x` by the sum of the `Mweight` of all other contending `RCIDs`. This
ratio `P` is determined by <<eq-3>>.
ratio `P` is determined by <<eq-4>>.

[latexmath#eq-4,reftext="equation ({counter:eqs})"]
++++
Expand Down
8 changes: 4 additions & 4 deletions qos_capacity.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -524,10 +524,10 @@ those capacity blocks. Next, the `cc_alloc_ctl register` is written to request a
`CONFIG_LIMIT` operation for the `RCID` and `AT`. Once a capacity allocation
limit has been established, a request may be allocated capacity in the _capacity
blocks_ allocated to the `RCID` and `AT` associated with the request. It is
important to note that at least one _capacity block_ must be allocated using
`cc_block_mask` when allocating capacity, or else the operation will fail with
`STATUS=5`. Overlapping _capacity block_ masks among `RCID` and/or `AT` are
allowed to be configured.
important to note that some implementations may require at least one _capacity
block_ to be allocated using `cc_block_mask` when allocating capacity;
otherwise, the operation will fail with `STATUS=5`. Overlapping _capacity block_
masks among `RCID` and/or `AT` are allowed to be configured.

[NOTE]
====
Expand Down
Loading