Skip to content

Conversation

@oagniqgnat
Copy link
Contributor

@oagniqgnat oagniqgnat commented Jan 8, 2026

Modification

Pptimize the performance of the 'Combine Ant Moving' function by removing several broad PipeBarrier<PIPE_ALL>() calls that likely introduced unnecessary waiting, and replacing one with a more granular SyncFuncAscendC::HardEvent::MTE2_S().

Benchmarking and Profiling

  • hidden=4096
image image image
  • hidden=7168
image image image

Checklist

@gemini-code-assist
Copy link
Contributor

Summary of Changes

Hello @oagniqgnat, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on optimizing the performance of the 'Combine Ant Moving' function by refining its internal synchronization mechanisms. The primary approach involves removing several broad PipeBarrier<PIPE_ALL>() calls that likely introduced unnecessary waiting, and replacing one with a more granular SyncFunc<AscendC::HardEvent::MTE2_S>(). This targeted adjustment aims to streamline execution flow and enhance efficiency within the CamMoeCombineNormalMultiRound class.

Highlights

  • Synchronization Refinement: Multiple instances of the broad PipeBarrier<PIPE_ALL>() synchronization primitive have been removed from various methods within the CamMoeCombineNormalMultiRound class.
  • Targeted Synchronization: One instance of PipeBarrier<PIPE_ALL>() was replaced with a more specific SyncFunc<AscendC::HardEvent::MTE2_S>(), indicating a move towards finer-grained and more efficient synchronization.
  • Performance Optimization: These changes are aimed at reducing unnecessary global synchronization overhead, thereby improving the overall performance of the 'Combine Ant Moving' function by allowing operations to proceed without excessive waiting.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

Copy link
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces performance optimizations to the CamMoeCombineNormalMultiRound function by refining its synchronization strategy. The changes primarily consist of removing redundant PipeBarrier<PIPE_ALL>() calls where synchronization is already handled by other mechanisms later in the code flow. Additionally, one general-purpose barrier has been replaced with a more specific and efficient SyncFunc to target only the necessary hardware unit.

These modifications are well-reasoned and demonstrate a solid understanding of the underlying hardware's synchronization primitives, which is crucial for low-level kernel optimization. The changes should lead to improved performance without compromising correctness. The overall implementation is of high quality.

@oagniqgnat oagniqgnat force-pushed the combine_long_seq_optimize branch from a2fe290 to c84376f Compare January 8, 2026 11:59
@oagniqgnat oagniqgnat closed this Jan 13, 2026
@oagniqgnat oagniqgnat deleted the combine_long_seq_optimize branch January 13, 2026 04:07
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