Expose lu_factor_batched_cublas#73877
Conversation
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in linalg.lu_solve. [ghstack-poisoned]
CI Flow Status⚛️ CI FlowRuleset - Version:
|
🔗 Helpful links
✅ No Failures (0 Pending)As of commit cbb7fdf (more details on the Dr. CI page): Expand to see more💚 💚 Looks good so far! There are no failures yet. 💚 💚 This comment was automatically generated by Dr. CI (expand for details).Please report bugs/suggestions to the (internal) Dr. CI Users group. |
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in linalg.lu_solve. [ghstack-poisoned]
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in linalg.lu_solve. [ghstack-poisoned]
|
pytorch/aten/src/ATen/native/cuda/linalg/BatchLinearAlgebraLib.cpp Lines 293 to 295 in bd13bc6 Also the description of the PR that added this function says |
|
For what is worth, that PR just tested up to batches of 4 matrices, which is not very representative either. |
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in linalg.lu_solve. [ghstack-poisoned]
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in linalg.lu_solve. [ghstack-poisoned]
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in linalg.lu_solve. [ghstack-poisoned]
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in linalg.lu_solve. [ghstack-poisoned]
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in linalg.lu_solve. [ghstack-poisoned]
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in `linalg.lu_factor`. [ghstack-poisoned]
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in `linalg.lu_factor`. [ghstack-poisoned]
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in `linalg.lu_factor`. [ghstack-poisoned]
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in `linalg.lu_factor`. [ghstack-poisoned]
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in `linalg.lu_factor`. [ghstack-poisoned]
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in `linalg.lu_factor`. [ghstack-poisoned]
| auto a_ptr_array_data = reinterpret_cast<scalar_t**>(a_ptr_array.data_ptr()); | ||
|
|
||
| at::cuda::blas::getrfBatched(n, a_ptr_array_data, lda, pivots_data, infos_data, batch_size); | ||
| #endif |
There was a problem hiding this comment.
This one handles non-contiguous inputs, right? Or is it done one level above in the stack?
There was a problem hiding this comment.
non-contiguous inputs are handled in the parent fucntion, that is, in linalg_lu_factor
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in `linalg.lu_factor`. [ghstack-poisoned]
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in `linalg.lu_factor`. [ghstack-poisoned]
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in `linalg.lu_factor`. [ghstack-poisoned]
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in `linalg.lu_factor`. [ghstack-poisoned]
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in `linalg.lu_factor`. [ghstack-poisoned]
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in `linalg.lu_factor`. [ghstack-poisoned]
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in `linalg.lu_factor`. [ghstack-poisoned]
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in `linalg.lu_factor`. [ghstack-poisoned]
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in `linalg.lu_factor`. [ghstack-poisoned]
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in `linalg.lu_factor`. [ghstack-poisoned]
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in `linalg.lu_factor`. [ghstack-poisoned]
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in `linalg.lu_factor`. [ghstack-poisoned]
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in `linalg.lu_factor`. [ghstack-poisoned]
Summary: We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in linalg.lu_solve. Pull Request resolved: #73877 Approved by: https://github.com/nikitaved, https://github.com/IvanYashchuk, https://github.com/mruberry Test Plan: contbuild & OSS CI, see https://hud.pytorch.org/commit/pytorch/pytorch/1880d293b64badac1b74e9c6bb0152e3950d3f7e Reviewed By: osalpekar Differential Revision: D37089123 Pulled By: osalpekar fbshipit-source-id: 55989cba1b2f8e0cbb1b7dae326bf2e52e3b0fb5
We had bindings for this function, but they were not exposed as a function inside ATen. This PR exposes them. This function is tested in the next PR of the stack, where it is used in linalg.lu_solve. Pull Request resolved: pytorch#73877 Approved by: https://github.com/nikitaved, https://github.com/IvanYashchuk, https://github.com/mruberry
Stack from ghstack:
We had bindings for this function, but they were not exposed as a
function inside ATen. This PR exposes them.
This function is tested in the next PR of the stack, where it is used in
linalg.lu_factor.