| 6 Mar 2023 |
 hexa |
FBGEMM (Facebook GEneral Matrix Multiplication) is a low-precision, high-performance matrix-matrix multiplications and convolution library
| 23:09:25 |
 SomeoneSerge (matrix works sometimes) | ❯ nix log nixpkgs#python3Packages.torch
...
-- USE_EIGEN_FOR_BLAS : ON
-- USE_FBGEMM : ON
-- USE_FAKELOWP : OFF
-- USE_KINETO : ON
...
| 23:09:47 |
| 7 Mar 2023 |
| SomeoneSerge (matrix works sometimes) | (how does one get an nvim diffsplit online?) | 00:01:28 |
| SomeoneSerge (matrix works sometimes) | Meanwhile, two notable GLIBCXX_3.4.30 failures remain: python3Packages.jax and python3Packages.torchvision | 00:39:55 |
| SomeoneSerge (matrix works sometimes) | Same error I saw with gpflow, something about scipy/optimize:
from ._highs._highs_wrapper import _highs_wrapper
E ImportError: /nix/store/205vsmbfhq1q2vhgskpqyymqvba4mscp-gcc-11.3.0-lib/lib/libstdc++.so.6: version `GLIBCXX_3.4.30' not found (required by /nix/store/yi7jc5p2mlwb3j37j7gwj15bk45j6xqs-python3.10-scipy-1.9.3/lib/python3.10/site-packages/scipy/optimize/_highs/_highs_wrapper.cpython-310-x86_64-linux-gnu.so)
| 00:40:34 |
| SomeoneSerge (matrix works sometimes) | * Meanwhile, two notable GLIBCXX_3.4.30 failures remain: python3Packages.jax (not jaxlib) and python3Packages.torchvision | 01:21:16 |
| SomeoneSerge (matrix works sometimes) | MKL -> down to 5s | 01:29:23 |
| SomeoneSerge (matrix works sometimes) | Mystery solved, I guess | 01:29:38 |
| SomeoneSerge (matrix works sometimes) | connor (he/him): you should've received an automated invite to the NixOS GH organization back when your first PR was merged. I don't see NixOS in your org list. Could you have missed it? | 12:07:02 |
| SomeoneSerge (matrix works sometimes) | * connor (he/him): you should've received an automated invite to the NixOS GH organization back when your first PR was merged. I don't see NixOS in your org list. Could you have missed it?
EDIT: Oh! That's how it works: https://github.com/NixOS/nixpkgs/issues/50105#issuecomment-1458140917
Add yourself to maintainers/maintainer-list.nix
| 13:16:35 |
| hexa | from where do I get nvcc? | 14:30:56 |
| hexa | nix-locate is being entirely unhelpful | 14:31:10 |
| hexa | I suspect somewhere below cudatoolkit? | 14:31:24 |
 Kevin Mittman (UTC-7) | cuda_nvcc ? | 15:08:10 |
| hexa | oh, thanks | 15:18:25 |
| hexa | a bit redundant, below cudaPackages | 15:18:36 |
| SomeoneSerge (matrix works sometimes) | In reply to @hexa:lossy.network
a bit redundant, below cudaPackages Yea, but the names come from the json manifests published by nvidia. And if we strip cuda_ from cuda_nvcc, should we keep lib in libcublas? And then you learn that libcusparse and cuSPARSE are different things | 16:30:18 |
| SomeoneSerge (matrix works sometimes) | ...maybe we just keep things as they are | 16:30:30 |
| SomeoneSerge (matrix works sometimes) | And work on discoverability/documentation more | 16:30:38 |
| hexa | 🙂 | 16:30:54 |
| SomeoneSerge (matrix works sometimes) | (also, the prefix goes well with inherit (cudaPackages) ... and with cudaPackages; | 16:33:17 |
| SomeoneSerge (matrix works sometimes) | * (also, the prefix goes well with inherit (cudaPackages) ... and with cudaPackages;) | 16:33:20 |
| Kevin Mittman (UTC-7) | Correction: libcusparse == cuSPARSE, which ships with CUDA SDK. However, libcusparse_lt == cuSPARSE Lt, which is its own thing | 22:07:20 |
| 8 Mar 2023 |
 connor (he/him) | All, if you're a maintainer let me know if you can see the project I made here: https://github.com/orgs/NixOS/teams/cuda-maintainers/projects?query=is%3Aopen | 00:54:15 |
| connor (he/him) | Direct link to the project: https://github.com/orgs/NixOS/projects/27
It's a private project because that seems to be the default; I gave the CUDA maintainers team admin access so it could be changed to public if that's of interest.
I spent a little bit of time going through open issues on Nixpkgs which are at all related to CUDA and added them to the swim lane named "New." If any don't belong on this project (for example, because it falls outside the scope of this maintainer group), please feel free to remove it.
I haven't figured out a way to have new issues tagged with the CUDA topic automatically added to the project, but I figure this is a good start to get some visibility into what's currently open. | 00:57:41 |
| SomeoneSerge (matrix works sometimes) | connor (he/him): that's so great! | 00:59:52 |
| SomeoneSerge (matrix works sometimes) | Yes, can see it | 00:59:56 |
| SomeoneSerge (matrix works sometimes) | https://github.blog/changelog/2023-01-19-github-issues-january-19th-update/
Seems that we need this special "auto-add to project" workflow | 01:04:50 |
| connor (he/him) | Hopefully the "by assignee" and "by status" views will be helpful too (tabular instead of Kanban) | 01:05:19 |
| connor (he/him) | Damn enterprise-grade features ;( | 01:06:36 |
