Skip to content
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.

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

#16812: Reordering cbs in reduce_init_delta #16981

Merged
merged 1 commit into from
Jan 29, 2025
Merged

Conversation

atatuzunerTT
Copy link
Contributor

@atatuzunerTT atatuzunerTT commented Jan 22, 2025

Ticket

Link to Github Issue

Problem description

In all compute kernel APIs, the ordering of the circular buffer parameters are input cbs first, then output cbs. However, in the reduce_init_delta function in the reduce.h kernel, the output cb parameter comes before those of input cbs. This may cause confusion (and it has in some files) as the expected ordering is inputs first and outputs later, following all other kernel APIs.

What's changed

The parameters were reordered such that the input cbs come before the output cb. Call chains were updated accordingly.

Checklist

  • Post commit CI passes
  • Blackhole Post commit (if applicable)
  • Model regression CI testing passes (if applicable)
  • Device performance regression CI testing passes (if applicable)
  • (For models and ops writers) Full new models tests passes
  • New/Existing tests provide coverage for changes

@atatuzunerTT atatuzunerTT merged commit ec23429 into main Jan 29, 2025
9 of 10 checks passed
@atatuzunerTT atatuzunerTT deleted the atuzuner/cb_reorder branch January 29, 2025 18:20
williamlyTT pushed a commit that referenced this pull request Jan 30, 2025
### Ticket
[Link to Github
Issue](#16812)

### Problem description
In all compute kernel APIs, the ordering of the circular buffer
parameters are input cbs first, then output cbs. However, in the
reduce_init_delta function in the reduce.h kernel, the output cb
parameter comes before those of input cbs. This may cause confusion (and
it has in some files) as the expected ordering is inputs first and
outputs later, following all other kernel APIs.

### What's changed
The parameters were reordered such that the input cbs come before the
output cb. Call chains were updated accordingly.

### Checklist
- [x] [Post commit CI
passes](https://github.com/tenstorrent/tt-metal/actions/runs/12917899606)
- [x] [Blackhole Post
commit](https://github.com/tenstorrent/tt-metal/actions/runs/12917901314)
(if applicable)
- [ ] Model regression CI testing passes (if applicable)
- [ ] Device performance regression CI testing passes (if applicable)
- [ ] **(For models and ops writers)** Full [new
models](https://github.com/tenstorrent/tt-metal/actions/workflows/full-new-models-suite.yaml)
tests passes
- [ ] New/Existing tests provide coverage for changes
yieldthought pushed a commit that referenced this pull request Jan 31, 2025
### Ticket
[Link to Github
Issue](#16812)

### Problem description
In all compute kernel APIs, the ordering of the circular buffer
parameters are input cbs first, then output cbs. However, in the
reduce_init_delta function in the reduce.h kernel, the output cb
parameter comes before those of input cbs. This may cause confusion (and
it has in some files) as the expected ordering is inputs first and
outputs later, following all other kernel APIs.

### What's changed
The parameters were reordered such that the input cbs come before the
output cb. Call chains were updated accordingly.

### Checklist
- [x] [Post commit CI
passes](https://github.com/tenstorrent/tt-metal/actions/runs/12917899606)
- [x] [Blackhole Post
commit](https://github.com/tenstorrent/tt-metal/actions/runs/12917901314)
(if applicable)
- [ ] Model regression CI testing passes (if applicable)
- [ ] Device performance regression CI testing passes (if applicable)
- [ ] **(For models and ops writers)** Full [new
models](https://github.com/tenstorrent/tt-metal/actions/workflows/full-new-models-suite.yaml)
tests passes
- [ ] New/Existing tests provide coverage for changes
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.

7 participants