Skip to content

Tweak wording for matmul blog #22

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.

Sign up for GitHub

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

Merged
merged 1 commit into from
Nov 20, 2024
Merged

Tweak wording for matmul blog #22

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions blog/2024-11-21-optimizing-matrix-mul/index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -260,13 +260,13 @@ Porting to Rust GPU went quickly, as the kernels Zach used were fairly simple. M
the time was spent with concerns that were not specifically about writing GPU code. For
example, deciding how much to abstract vs how much to make the code easy to follow, if
everything should be available at runtime or if each kernel should be a compilation
target, etc. The code is still not _great_ as it is still blog post code!
target, etc. The code is not _great_ as it is still blog post code!

My background is not in GPU programming, but I do have Rust experience. I joined the
Rust GPU project because I tried to use standard GPU languages and knew there must be a
better way. Writing these GPU kernels felt like writing any other Rust code (other than
debugging, more later) which is a huge win to me. Not only the language itself, but the
entire development experience.
debugging, more on that later) which is a huge win to me. Not only the language itself,
but the entire development experience.

## Rust-specific party tricks

Expand Down