Skip to content

Conversation

aviralni
Copy link
Contributor

@aviralni aviralni commented Jun 2, 2025

Related-To: VLCLJ-2505

@aviralni aviralni force-pushed the mem_cts branch 2 times, most recently from 7c5d16c to 8dfacd5 Compare June 11, 2025 10:29
@vishnu-khanth
Copy link
Contributor

@aviralni Is this test expected to pass in all platforms?
If not, proper capability should be defined for filtering out this test from unsupported platforms!

LOG_INFO << "Percentage Bandwidth: " << percentage_bandwidth << "%";
EXPECT_GT(percentage_bandwidth, 0.0)
<< "Percentage bandwidth is not greater than zero";
EXPECT_LT(percentage_bandwidth, 100.0)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LE ?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is it possible to reach 100% utilization?


// Get initial bandwidth counters
auto bandwidth_before = lzt::get_mem_bandwidth(mem_handle);
EXPECT_LT(bandwidth_before.readCounter, UINT64_MAX);
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

readCounter & WriteCounter < UNIT64_MAX checks may not be useful.

maxBandWidth & timestamp can be checked if it's greater than 0. (Instead of checking < UNIT64_MAX )

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actually, these checks were already present for counters validation, so did not modify these. IMO too we can modify these checks.

@vishnu-khanth
Copy link
Contributor

LGTM.
@anvesh-intel / @pratikbariintel to confirm if this test case covers the issue recently seen with bandwidth counters.

@pratikbariintel
Copy link
Contributor

lgtm

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.

5 participants