-
Notifications
You must be signed in to change notification settings - Fork 99
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
initial implementation of new ETI #526
Conversation
|
New PR instead of canceled #526 |
Please make sure to test with Trilinos as well as the |
Testing to-dos:
|
SET(EXECSPACE_SERIAL_VALID_MEM_SPACES HBWSPACE HOSTSPACE CUDAUVMSPACE) | ||
SET(EXECSPACE_OPENMP_VALID_MEM_SPACES HBWSPACE HOSTSPACE CUDAUVMSPACE) | ||
SET(EXECSPACE_PTHREAD_VALID_MEM_SPACES HBWSPACE HOSTSPACE CUDAUVMSPACE) | ||
SET(EXECSPACE_SERIAL_VALID_MEM_SPACES HBWSPACE HOSTSPACE) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jjwilke do these changes for valid mem spaces need to propagate to develop independent of this PR?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, this is only an ETI thing.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so we're double-instantiating all those kernels? sadness :(
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we were before, too? This PR is a "preserve all existing behavior". The next PR would do the anon spaces stuff.
One thing at a time!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@jjwilke praise Turing and pass the ammunition ;-)
I had to make quite a few changes for blake to various things, independent of the ETI. |
@jjwilke can you cherry-pick these changes for a separate PR? |
Cherry-picked changes here: #533 |
Timing data on kokkos-dev-2,
|
7791c91
to
858300f
Compare
858300f
to
8b2b5c8
Compare
Unsuccessful test on kokkos-dev-2, spot-check with cm_test_all_sandia script
Looks like linking errors with the trsm update:
etc |
8b2b5c8
to
94ae52d
Compare
Yeah, somehow I managed to rebase with no conflicts without actually adding On both develop and the branch, I'm getting |
Tests on kokkos-dev-2 look better:
The failing clang build is due to |
White spot-check testing with cm_test_all_sandia looks good. gcc tests passed, I had to restart tests after with corrected arch options, below is output for xl and cuda:
|
We pushed the one file per ETI instance change, right ? Thanks for keeping track of the times. |
Yes, the most recent commit does one ETI instance per file for better parallelism. |
@jjwilke Thank you ! |
@jjwilke Is this ready to go in to develop ? |
@srajama1 we need to convert testing to the cm_* scripts first, or else nearly all our nightlies will begin failing. |
I believe this is ready. Obviously we'll want some extensive testing. |
@jjwilke the nightlies are now testing with the cmake build system, so that blocker is removed from this PR. |
94ae52d
to
bf2038e
Compare
I would merge the TPL PR #546, then merge this. I this branch has been rebased and should be ready to merge. Someone will want to make sure all the recent SPILUK, SPTRSV changes are still working in this branch. |
7906fb0
to
b0e1e79
Compare
@ndellingwood spot-check and spot-check-tpls are all passing on kokkos-dev-2. I think this is ready to go. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm based on passing tests and seeming to be safe with last round of integration testing, this is awesome @jjwilke ! There were a lot of files to scroll down, did I miss instructions for how devs should update the build system when adding new capabilities? That can be added later if not in this PR
@@ -0,0 +1,36 @@ | |||
#! /usr/bin/env python |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't write python code often, wanted to check if this is python 2 vs 3 agnostic?
@jjwilke arg, I dropped another merge conflict on you, sorry... |
@jjwilke if you have time to clean up the merge conflict (sorry for another) I think we're good to merge this in? |
Rebased. Ready to go? |
Merging that was like our version of "the snap" |
No description provided.