triton-ascend-case-reduction-amax-large

Map reduce axes to multiple cores with atomic operations on Ascend hardware.

6|1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/xchang1121/AutoResearch-CC-hook --skill triton-ascend-case-reduction-amax-large
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triton-ascend-case-reduction-amax-large
Source: https://github.com/xchang1121/AutoResearch-CC-hook/tree/main/skills/triton-ascend/cases/triton-ascend-case-reduction-amax-large
Command: npx skills add https://github.com/xchang1121/AutoResearch-CC-hook --skill triton-ascend-case-reduction-amax-large

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Reduces the bottleneck of large-axis reductions by mapping the reduce axis to multiple cores and performing atomic reductions across thread blocks, avoiding common UB issues in extreme configurations.

Core Features & Use Cases

  • Maps the reduce axis to multi-core execution to improve throughput on large N.
  • Uses atomic operations for intra-kernel reductions and two-stage tiling to maximize occupancy.
  • Suitable for extreme shape ratios like M<<N (e.g., 16×262144) on Ascend hardware.

Quick Start

Run the Triton Ascend case with the provided grid and atomic-min reduction strategy to verify performance on large-scale reductions.

Frequently Asked Questions about triton-ascend-case-reduction-amax-large

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I optimize large-axis reductions in Triton on Ascend hardware?

Optimize large-axis reductions in Triton by mapping the reduce axis to multiple cores and performing atomic reductions across thread blocks. This approach minimizes UB issues and maximizes throughput for extreme configurations.

Does Triton support multi-core execution with atomic operations for extreme shape ratios?

Yes, Triton supports multi-core execution with atomic operations for extreme shape ratios like 16×262144. It applies grid partitioning across the reduce dimension and two-stage tiling to improve occupancy on Ascend hardware.

What is the best way to handle extreme shape ratios where the non-reduce axis is small?

Handle extreme shape ratios where the non-reduce axis is small by using configurable autotune settings and atomic-min reduction strategies. This maps large reduce axes to multiple cores to avoid bottlenecks.

Why does large-scale reduction cause bottlenecks and how does two-stage tiling help?

Large-scale reduction causes bottlenecks due to single-core processing limits. Two-stage tiling helps by partitioning the grid across the reduce dimension and using atomic operations, maximizing occupancy and throughput on Ascend.

Can I use grid partitioning across the reduce dimension to minimize UB issues?

Yes, you can use grid partitioning across the reduce dimension to minimize UB issues. By mapping the reduce axis to multiple cores with atomic operations, the kernel avoids common UB issues found in extreme configurations.

When should I use atomic reductions for parallel kernel optimization on Ascend?

Use atomic reductions for parallel kernel optimization on Ascend when dealing with extreme shape ratios where the non-reduce axis is small and the reduce axis is large, such as 16×262144, to maximize throughput.