File tree 1 file changed +3
-3
lines changed
blog/2024-11-25-optimizing-matmul
1 file changed +3
-3
lines changed Original file line number Diff line number Diff line change @@ -23,7 +23,7 @@ his blog post!
23
23
::: tip
24
24
25
25
The complete runnable code can be [ found on
26
- GitHub] ( https://github.com/Rust-GPU/rust-gpu.github.io/tree/main/blog/2024-11-21 -optimizing-matrix-mul /code ) .
26
+ GitHub] ( https://github.com/Rust-GPU/rust-gpu.github.io/tree/main/blog/2024-11-25 -optimizing-matmul /code ) .
27
27
28
28
:::
29
29
@@ -307,7 +307,7 @@ leave the "fancier" experiments for another time.
307
307
308
308
I didn't include performance numbers as I have a different machine than Zach. The
309
309
complete runnable code can be [ found on
310
- GitHub] ( https://github.com/Rust-GPU/rust-gpu.github.io/tree/main/blog/2024-11-21 -optimizing-matrix-mul /code )
310
+ GitHub] ( https://github.com/Rust-GPU/rust-gpu.github.io/tree/main/blog/2024-11-25 -optimizing-matmul /code )
311
311
and you can run the benchmarks yourself with ` cargo bench ` .
312
312
313
313
::: tip
@@ -325,7 +325,7 @@ my time was spent with concerns that were not specifically about writing GPU cod
325
325
example, deciding how much to abstract vs how much to make the code easy to follow, if
326
326
everything should be available at runtime or if each kernel should be a compilation
327
327
target, etc. [ The
328
- code] ( https://github.com/Rust-GPU/rust-gpu.github.io/tree/main/blog/2024-11-21 -optimizing-matrix-mul /code )
328
+ code] ( https://github.com/Rust-GPU/rust-gpu.github.io/tree/main/blog/2024-11-25 -optimizing-matmul /code )
329
329
is not _ great_ as it is still blog post code!
330
330
331
331
My background is not in GPU programming, but I do have Rust experience. I joined the
You can’t perform that action at this time.
0 commit comments