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

[QST]Is the Key Difference Between mbarrier and barrier Their Handling of Producer-Consumer Count? #1999

Open
ziyuhuang123 opened this issue Dec 18, 2024 · 3 comments

Comments

@ziyuhuang123
Copy link

Barrier is used for scenarios where the number of producers and consumers is the same, while mbarrier is used when the numbers differ.

Is this conclusion correct? Is this the fundamental difference and design intent between mbarrier and barrier?

Copy link

This issue has been labeled inactive-30d due to no recent activity in the past 30 days. Please close this issue if no further response or action is needed. Otherwise, please respond with a comment indicating any updates or changes to the original issue and/or confirm this issue still needs to be addressed. This issue will be labeled inactive-90d if there is no activity in the next 60 days.

@hwu36
Copy link
Collaborator

hwu36 commented Mar 4, 2025

@Junkai-Wu

@Junkai-Wu
Copy link
Contributor

This conclusion is incorrect. Both barrier and mbarrier are based on arrive-wait mechanism. This mechanism doesn't necessary require the number of producer and consumer is the same.

mbarrier is more flexible and powerful than barrier. mbarrier has two modes, one is arrive wait which is similar as barrier. The other is transaction wait which barrier doesn't support.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants