-
Notifications
You must be signed in to change notification settings - Fork 17
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
No example of using hardware path #11
Comments
Hello @optimistyzy, thank you for raising an issue. It seems for me that Job API examples are completely unusable in the current state, they definitely should be reworked. As for High Level API examples, the only change that is required to run hardware path is change the line: using execution_path = dml::software; to: using execution_path = dml::hardware; In any case, I added the issue to bug tracker. |
Thanks. From my usage experience, So better to add this to make it clear. |
There is a part of REAMDE.md which describes how to build the library with hardware path enabled. That extra step is likely to be removed in future releases. Regarding configuration, the library relies on idxd-config documentation, which is linked in reference manual. |
@EgorKupaev I know this. What I means that we at least need a example to use hw path with a very simple description. |
@EgorKupaev man, I also need a quick example that can run over HW path. as I am new to DSA, I do not know how many places code I need change to make this happen. and also I also need one example copy from DRAM to pmem |
Hi @gaowayne, just wanted to let you know that we're working on improving this area for DML. |
From the current examples, there is no detailed guide and code on how to use the hardware path.
The text was updated successfully, but these errors were encountered: