Skip to content

Curated References

This is the detailed catalog behind the Resources Hub. The goal is not to dump links; it is to show which source helps with which kind of SGEMM question.

How to use this page

  • Start with the Resources Hub if you need help choosing a route.
  • Use this page when you already know the category of source you need.
  • Continue to Further Reading Routes when the right next topic matters more than the right citation.

Official CUDA and NVIDIA docs

These are the sources to open when you need precise constraints, terminology, or API behavior.

Why this shelf matters:

  • It anchors whitepaper claims in vendor-defined behavior instead of community folklore.
  • It helps you explain why unsupported shapes, alignment limits, and fallback rules are engineering constraints, not arbitrary policy.

Papers and performance mental models

Open this shelf when you want the design logic behind SGEMM optimization rather than raw API detail.

Why this shelf matters:

  • It gives readers a mental model for why the kernel ladder is ordered the way it is.
  • It helps you discuss performance ceilings without reducing everything to one benchmark number.

Exemplary codebases and production-grade samples

Open this shelf when you want to compare this repository's explanatory style with industrial-strength implementations.

Why this shelf matters:

  • It shows where this repository is deliberately simplified for teaching.
  • It gives interview follow-up material when someone asks what the "next production step" would look like.

Profiler, tooling, and diagnosis references

Open this shelf when a benchmark number stops being self-explanatory and you need evidence.

Why this shelf matters:

Engineering workflow and validation discipline

Open this shelf when the question is about proving correctness, structuring builds, or keeping claims reproducible.

  • GoogleTest Documentation
    Best for understanding the local correctness harness and tolerance-oriented testing vocabulary.
  • CMake Documentation
    Best for build-system expectations, generator behavior, and reproducible local setup.
  • OpenSpec documentation
    Best for understanding the spec-governed documentation and change workflow used in this repository.

Why this shelf matters:

  • It reinforces the repository's local-GPU versus hosted-CI boundary model.
  • It explains why "performance proof" and "repository integrity" live on different evidence surfaces.

Next-step study routes

Use these when you know you want to keep learning, but not which topic should come first.

MIT Licensed