Skip to content

Conversation

joserochh
Copy link
Contributor

@joserochh joserochh commented Aug 21, 2025

Proposed changes

Optimize linking removing unnecessary memory transactions at cinst (for metadata) and minst levels.

Types of changes

What types of changes does your code introduce to the Encrypted Computing SDK project?
Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Documentation update (if none of the other choices apply)

Checklist

Put an x in the boxes that apply. You can also fill these out after creating
the PR. If you are unsure about any of them, do not hesitate to ask. We are
here to help! This is simply a reminder of what we are going to look for before
merging your code.

  • I have read the CONTRIBUTING agreement
  • Current formatting and unit tests / base functionality passes locally with my changes
  • I have added tests that prove my fix is effective or that my feature works (if appropriate)
  • I have added necessary documentation (if appropriate)
  • Any dependent changes have been merged and published in downstream modules

Further comments

With this implementation an minst from multi-individual kernel operations linking looks pretty much the same as an minst from a big unified multi op kernel. That was also achieved at .mem level on previous PR and it partially achieved now at cinst level by removing metadata memory transactions.

Apart from the unit-tests integration tests have been added to validate the entire linking flow.

@joserochh joserochh marked this pull request as ready for review August 21, 2025 23:34
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