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

Refactor operators to methods. #2

Open
IkonOne opened this issue May 18, 2021 · 0 comments
Open

Refactor operators to methods. #2

IkonOne opened this issue May 18, 2021 · 0 comments

Comments

@IkonOne
Copy link
Owner

IkonOne commented May 18, 2021

As it stands, thrust::for_each calls using the operators incur memory transfer penalties for each call (to and from device). However, this structure also makes it super easy to test the methods. The key decisions that need to be made are:

  • Does it make sense for each functional unit to be it's own struct/operator when they are stateless?
  • Should they just be methods?
  • If they are methods, how would they be used?
  • Can we keep them as operators and avoid the host/device memory transfer cost?
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

1 participant