-
Notifications
You must be signed in to change notification settings - Fork 29
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
Add exporting with argument device affinities #300
Conversation
This requires iree-org/iree-turbine#231. |
sharktank/sharktank/export.py
Outdated
module_fn_with_flat_signature, | ||
*transitive_args, | ||
args=flat_args, | ||
argument_device_affinities=argument_device_affinities, |
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.
Wait, where does this actually plumb through? I don't see this as part of the 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.
I see, the changes are dependent on https://github.com/iree-org/iree-turbine/pull/231/files
Lets focus on that and shelve these changes. Once export
has the right parameter we won't need to make the sharktank changes.
c9404c0
to
0eb437f
Compare
0eb437f
to
9d35b3d
Compare
We don't have handling of device affinties for our sharded tensor types when they are the arguments of exported functions. Although, they can be specified explicitly when exporting, this change adds the ability to hide this and deduces the affinties from the tensor types.
9d35b3d
to
abbabed
Compare
We don't have handling of device affinties for our sharded tensor types when they are the arguments of exported functions. Although, they can be specified explicitly when exporting, this change adds the ability to hide this and deduces the affinties from the tensor types.