Skip to content

Randomize Python backend shared memory region naming #351

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

Merged
merged 3 commits into from
Apr 8, 2024
Merged

Conversation

Tabrizian
Copy link
Member

@Tabrizian Tabrizian commented Apr 5, 2024

I did some testing with 10 regions and everything seems to work fine.

@Tabrizian Tabrizian requested review from kthui and nnshah1 April 5, 2024 16:19
Copy link
Contributor

@rmccorm4 rmccorm4 left a comment

Choose a reason for hiding this comment

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

Should we update that README section on shm region name collision and setting a prefix and such?

Copy link
Contributor

@kthui kthui left a comment

Choose a reason for hiding this comment

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

LGTM! We could probably mark the setting prefix option on the README as deprecated, because it is no longer necessary to avoid naming collision.

@Tabrizian
Copy link
Member Author

@rmccorm4 @jackyh docs are updated.

@Tabrizian Tabrizian requested review from rmccorm4 and kthui April 5, 2024 21:23
@Tabrizian Tabrizian merged commit 4d42111 into main Apr 8, 2024
3 checks passed
@Tabrizian Tabrizian deleted the imant-shm-fix branch April 8, 2024 17:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

3 participants