Skip to content
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

Parallelize fixes #807

Merged
merged 3 commits into from
Sep 3, 2024
Merged

Conversation

mmichal10
Copy link
Contributor

No description provided.

Signed-off-by: Robert Baldyga <[email protected]>
Signed-off-by: Michal Mielewczyk <[email protected]>
In some scenarios running the exact number of shards, regardless of
number of available queues is crucial for correctness of operation.

Signed-off-by: Robert Baldyga <[email protected]>
Signed-off-by: Michal Mielewczyk <[email protected]>
In situation when all the shards finish their work before parallelize
loop does it's final loop condition check, which involves access to
parallelize object, it's possible that parallelize object will be
deinitialized before this final access.

Increasing refcount by 1 before running parallelize and decreasing it
only after the loop is finished addresses this problem.

Signed-off-by: Robert Baldyga <[email protected]>
Signed-off-by: Michal Mielewczyk <[email protected]>
@robertbaldyga robertbaldyga merged commit 01902e1 into Open-CAS:master Sep 3, 2024
2 checks passed
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.

3 participants