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.

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

fix: Skip MAX_ACC_OUT_READ on the broken FW versions #36

Merged
merged 1 commit into from
Nov 1, 2024

Conversation

almaslennikov
Copy link
Collaborator

@almaslennikov almaslennikov commented Oct 29, 2024

According to the PRM, setting MAX_ACC_OUT_READ to zero enables the auto mode,
which applies the best suitable optimizations.
However, there is a bug in certain FW versions, where the zero value is not available.
In this case, until the fix is available, skipping this parameter and emitting a warning

@coveralls
Copy link

coveralls commented Oct 29, 2024

Pull Request Test Coverage Report for Build 11628576864

Details

  • 13 of 28 (46.43%) changed or added relevant lines in 3 files are covered.
  • 18 unchanged lines in 3 files lost coverage.
  • Overall coverage decreased (-0.3%) to 60.316%

Changes Missing Coverage Covered Lines Changed/Added Lines %
cmd/nic-configuration-daemon/main.go 0 1 0.0%
pkg/host/host.go 0 2 0.0%
pkg/host/configvalidation.go 13 25 52.0%
Files with Coverage Reduction New Missed Lines %
pkg/host/host.go 1 80.3%
pkg/host/configvalidation.go 1 88.53%
pkg/host/mocks/HostUtils.go 16 58.15%
Totals Coverage Status
Change from base Build 11591155294: -0.3%
Covered Lines: 1757
Relevant Lines: 2913

💛 - Coveralls

@almaslennikov almaslennikov marked this pull request as draft October 29, 2024 12:53
@almaslennikov almaslennikov marked this pull request as ready for review October 30, 2024 07:31
@almaslennikov almaslennikov force-pushed the max-acc-out-read branch 2 times, most recently from f60c301 to c3062d1 Compare November 1, 2024 10:52
@almaslennikov almaslennikov changed the title fix: use device defaults for MAX_ACC_OUT_READ on PCIe Gen5 fix: Skip MAX_ACC_OUT_READ on the broken FW, not set the default values if optimizations are disabled Nov 1, 2024
@almaslennikov almaslennikov changed the title fix: Skip MAX_ACC_OUT_READ on the broken FW, not set the default values if optimizations are disabled fix: Skip MAX_ACC_OUT_READ on the broken FW versions Nov 1, 2024
According to the PRM, setting MAX_ACC_OUT_READ to zero enables the auto mode,
which applies the best suitable optimizations.
However, there is a bug in certain FW versions, where the zero value is not available.
In this case, until the fix is available, skipping this parameter and emitting a warning

Signed-off-by: Alexander Maslennikov <[email protected]>
@almaslennikov almaslennikov merged commit 0154882 into Mellanox:main Nov 1, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants