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

Expose environment variable to force comms partitioning #1511

Open
maddyscientist opened this issue Nov 5, 2024 · 1 comment
Open

Expose environment variable to force comms partitioning #1511

maddyscientist opened this issue Nov 5, 2024 · 1 comment
Assignees
Labels
Milestone

Comments

@maddyscientist
Copy link
Member

We should expose an env to force loop-back communication on in a given dimension, as we have are able to using an API at present. This would allow us to switch on communication when QUDA is driven by an external application, e.g., Chroma or MILC. This would have the great benefit of enabling a reduction in node-hours spent on autotuning by doing most of the tuning at small scale.

@maddyscientist maddyscientist added this to the QUDA 2.0 milestone Nov 5, 2024
@maddyscientist maddyscientist self-assigned this Nov 5, 2024
@maddyscientist
Copy link
Member Author

@stevengottlieb FYI

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant