Update DWRR scheduler weight range #2188
Conversation
cc621a4 to
f163c86
Compare
|
@JaiOCP could you please review |
|
@eddyk-nvidia could you please review |
JaiOCP
left a comment
JaiOCP
left a comment
There was a problem hiding this comment.
Approving with the assumption that review comment would be taken care off
There was a problem hiding this comment.
Please update the comments reflecting the 8 bit value range 0..255, where 0 is invalid value
There was a problem hiding this comment.
@JaiOCP Updated the range to 0...255 and 0 as invalid weight
Signed-off-by: Kumaresh Perumal <kperumal@microsoft.com>
Signed-off-by: Kumaresh Perumal <kperumal@microsoft.com>
29cce00 to
9ce6019
Compare
|
/azp run |
|
Azure Pipelines successfully started running 1 pipeline(s). |
|
@rajkumar38, @ashutosh-agrawal - please help get this reviewed |
|
@ashutosh-agrawal @itaibaz Could you please review and approve the PR |
|
I think there was already a suggestion to add a new switch attribute, dwrr weight range, uint8 range, that will reflect the HW capabilities, for example [1..100] or [1..255] and would allow the application to query that |
Thanks @itaibaz Max DWRR weight using switch capability will be added in the later PRs. This PR is a minor change to only update the comment. |
* Update DWRR weight range Signed-off-by: Kumaresh Perumal <kperumal@microsoft.com>
6 participants
Current DWRR weight range is from 1-100, increase to 1-255 as some ASIC supports higher value.