Skip to content
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

Open
optimistyzy opened this issue Nov 26, 2021 · 6 comments
Open

No example of using hardware path #11

optimistyzy opened this issue Nov 26, 2021 · 6 comments
Assignees

Comments

@optimistyzy
Copy link

From the current examples, there is no detailed guide and code on how to use the hardware path.

@EgorKupaev
Copy link
Contributor

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.

@EgorKupaev EgorKupaev self-assigned this Nov 26, 2021
@optimistyzy
Copy link
Author

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.
Hi @EgorKupaev

Thanks. From my usage experience,
(1)It still needs some make file or cmake change if we use the hardware path.
(2) Configuring wqs by idxd-config.

So better to add this to make it clear.

@EgorKupaev
Copy link
Contributor

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.

@optimistyzy
Copy link
Author

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.

@gaowayne
Copy link

@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

@mzhukova
Copy link
Contributor

mzhukova commented Mar 3, 2023

Hi @gaowayne, just wanted to let you know that we're working on improving this area for DML.
We've extended Quick Start to provide some instruction on how to change current examples, so that they could be offloaded to accelerator, and additionally would be providing an option to specify execution path as input parameter for examples executables.
Hope this would make in clearer.

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

No branches or pull requests

4 participants