-
Notifications
You must be signed in to change notification settings - Fork 25
Zkcuda parallel witness #169
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
Conversation
|
Please merge this PR after #163. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Summary of Changes
Hello @siq1, 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 introduces parallel witness generation capabilities specifically within the Zkcuda backend. The core change involves refactoring the hint calling mechanism to be thread-safe, enabling the parallel evaluation of circuit components and hints during witness computation.
Highlights
- Hint Registry Update: The
HintRegistryhas been modified to store stateless function pointers (fn) instead of mutable closures (dyn FnMut). This change, along with adding theClonederive, makes the registry compatible with being shared across threads. - Parallel Witness Evaluation in Zkcuda: Within the
Zkcuda Context, I've introduced parallel processing using therayoncrate for evaluating IR kernels and hint solvers. Inputs for parallel tasks are now collected and processed concurrently. - API Signature Changes: Functions throughout the codebase that interact with a
HintCaller(e.g., evaluation and witness solving methods) have been updated to accept an immutable reference (&impl HintCaller) instead of a mutable one (&mut impl HintCaller). - Test Case Removal: A test case (
test_300_closure) into_binary_hint.rsthat relied on mutable state captured by a closure (which is incompatible with the new statelessfnrequirement for thread safety) has been removed.
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 in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.
| 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 issue 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 is currently in preview and 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 to provide feedback.
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
-
Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configureGemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩
There was a problem hiding this 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 refactors the hint execution mechanism to support parallel witness generation. Key changes include modifying HintCaller methods to take &self, adding a Sync bound to HintCaller, and changing HintRegistry to use function pointers (fn) for hints instead of Box<dyn FnMut>. These changes enable HintRegistry to be Clone and Sync, which is essential for parallel processing. A test relying on stateful closures has been removed as it's incompatible with the new design. Parallel execution is implemented in zkcuda::Context using Rayon.
No description provided.