Skip to content

perf(clr): Write AQL packets with non-temporal stores - #284

Open
saleelk wants to merge 1 commit into
ROCm:release/rocm-rel-6.3.0.1from
saleelk:users/saleelk/ntAqlWrite_63
Open

perf(clr): Write AQL packets with non-temporal stores#284
saleelk wants to merge 1 commit into
ROCm:release/rocm-rel-6.3.0.1from
saleelk:users/saleelk/ntAqlWrite_63

Conversation

@saleelk

@saleelk saleelk commented Sep 2, 2026

Copy link
Copy Markdown
Contributor

Assigning a packet into its ring buffer slot pulls that slot's cache line in for ownership and dirties it, which buys nothing: the packet processor is the only other reader and it fetches the slot over the fabric anyway.

Copy the 60 body bytes with non-temporal stores instead, so they land straight in the write-combining buffer, and keep publishing the header with the existing release store once an sfence has drained that buffer. The header dword stays out of the copy, so the slot holds the invalid header the packet processor left behind until the body has arrived. Covers kernel dispatch, barrier-AND and barrier-value packet submission.

Associated JIRA ticket number/Github issue number

What type of PR is this? (check all applicable)

  • Refactor
  • Feature
  • Bug Fix
  • Optimization
  • Documentation Update
  • Continuous Integration

What were the changes?

Why are these changes needed?

Updated CHANGELOG?

  • Yes
  • No, Does not apply to this PR.

Added/Updated documentation?

  • Yes
  • No, Does not apply to this PR.

Additional Checks

  • I have added tests relevant to the introduced functionality, and the unit tests are passing locally.
  • Any dependent changes have been merged.

Assigning a packet into its ring buffer slot pulls that slot's cache line
in for ownership and dirties it, which buys nothing: the packet processor
is the only other reader and it fetches the slot over the fabric anyway.

Copy the 60 body bytes with non-temporal stores instead, so they land
straight in the write-combining buffer, and keep publishing the header
with the existing release store once an sfence has drained that buffer.
The header dword stays out of the copy, so the slot holds the invalid
header the packet processor left behind until the body has arrived. Covers
kernel dispatch, barrier-AND and barrier-value packet submission.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant