PTX ISA 9.5 adds new async copy, fence and locality primitives for CUDA kernels
A post highlights PTX ISA 9.5 changes: stricter async copy waits, release fences for reads through aliased addresses, locality domain queries and timestamped trace markers, all tied to memory ordering and scheduling on recent GPUs.
By Wendelmaques Pereira · Updated today
Source: PTX ISA 9.5 adiciona novas instruções de cópia async, fence e locality (docs.nvidia.com). Text prepared with AI from this source.
What happened and what to do
The post highlights new features in PTX ISA 9.5, the version of the PTX intermediate language used by CUDA kernels. The changes include stricter async copy waits, release fences for reads made through aliased addresses, locality domain queries and timestamped trace markers. The post points to the official PTX ISA 9.5 documentation for the details of each instruction.
In practice, a company running CUDA kernels on its own inference or data processing infrastructure should check which parts use async copies and buffers with aliased addresses, since memory ordering at those points may behave differently with the new version. A safe path is to map the affected kernels, build ordering regression tests, add the trace markers to a profiling pipeline and send the results to a monitoring dashboard. Locality data can inform workload placement across GPUs where that matters for the case.
How the consultancy can help
Diagnosis of existing CUDA kernels and inference pipelines to identify async copies, reads through aliased addresses and synchronization points that depend on the new PTX ISA 9.5 primitives. Then a scoped implementation of memory ordering tests, trace markers and profiling dashboards on the client's infrastructure.
Next step
Send a short description of your case, including the type of GPU workload and the infrastructure where it runs, and receive a scoped diagnosis and implementation proposal.
Let's assess your project

I reply with scope and a proposal.