Skip to content

Handle default kernel behavior for CPU access to all NUMA nodes #533

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

Merged
merged 1 commit into from
Jun 12, 2024

Conversation

bratpiorka
Copy link
Contributor

@bratpiorka bratpiorka commented Jun 6, 2024

Description

For the default CPU memspace (MemspaceHostAll) with all NUMA nodes, we should follow the default kernel behavior, and we shouldn't call any kind of mbind() that could negatively impact the performance

Checklist

  • Code compiles without errors locally
  • All tests pass locally
  • CI workflows execute properly
  • New tests added, especially if they will fail without my changes

@bratpiorka bratpiorka force-pushed the rrudnick_default_numa branch 3 times, most recently from f6b6963 to 041be22 Compare June 10, 2024 07:32
@bratpiorka bratpiorka marked this pull request as ready for review June 10, 2024 08:00
@bratpiorka bratpiorka requested a review from a team as a code owner June 10, 2024 08:00
@bratpiorka bratpiorka force-pushed the rrudnick_default_numa branch from 041be22 to f74e0d5 Compare June 10, 2024 08:04
@bratpiorka bratpiorka requested a review from lplewa June 10, 2024 13:47
@bratpiorka bratpiorka force-pushed the rrudnick_default_numa branch from f74e0d5 to 5c893fe Compare June 11, 2024 07:17
@bratpiorka bratpiorka force-pushed the rrudnick_default_numa branch from 5c893fe to 13b0b68 Compare June 11, 2024 11:04
@bratpiorka bratpiorka merged commit c5735e4 into oneapi-src:main Jun 12, 2024
66 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