set job->numa_id = -3, not work
Open
- Dominant language
- C
- Stars
- 110
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
Test step:
1. only enable 1 IAA on socket 0
2. After qpl_init_job, set job->numa_id = -3 // QPL_DEVICE_NUMA_ID_ANY
3. run test app on NUMA 1, qpl_execute_job return error code 503 (QPL_STS_INIT_WORK_QUEUES_NOT_AVAILABLE)
The setting "job->numa_id = -3" seems not working.
Contributor guide
Research direction
Start by reproducing the issue with qpl_init_job and qpl_execute_job: enable one IAA on socket 0, set job->numa_id to -3, and run the test app on NUMA 1. Trace the NUMA selection and work-queue initialization, then verify that qpl_execute_job no longer returns QPL_STS_INIT_WORK_QUEUES_NOT_AVAILABLE.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c
- Domain
- operating-systems, performance
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100