We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
find_devices
Let's assume 2 warboy NPUs (namely, npu0 and npu1) with a core of npu1 occupied.
npu0
npu1
(npu0) {0: Available, 1: Available} (npu1) {0: Occupied("test"), 1: Available}
If someone is looking for an available singlecore devfile, it would be pleasant if find_devices(..) returns npu1pe1.
find_devices(..)
npu1pe1
But current implementation returns npu0pe0 since it does not consider fragmentation.
npu0pe0
[DeviceFile { device_index: 0, core_indices: [0], path: "/root/src/device-api/test_data/test-0/dev/npu0pe0", mode: Single }]
The text was updated successfully, but these errors were encountered:
I think we may need a delicate approach on this issue since, adopting greedy algorithm is improper in some situations.
ex) Assume a Renegade NPU (npu0) with 8 cores, with core indices 0, 1, 4 occupied (see diagram below).
0
1
4
If someone is looking for 2 singlecore devfiles, it would be best to return npu0pe2, npu0pe3.
npu0pe2
npu0pe3
But a step-by-step (greedy) approach may result in returning npu0pe5, npu0pe2.
npu0pe5
Sorry, something went wrong.
No branches or pull requests
Let's assume 2 warboy NPUs (namely,
npu0
andnpu1
) with a core ofnpu1
occupied.If someone is looking for an available singlecore devfile, it would be pleasant if
find_devices(..)
returnsnpu1pe1
.But current implementation returns
npu0pe0
since it does not consider fragmentation.The text was updated successfully, but these errors were encountered: