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.

Sign up for GitHub

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

Jump to bottom

libfabric-2.0: Completion changes (CQs and cntr) - Issue#9017 #26

Open
syskovprdap opened this issue Nov 14, 2024 · 0 comments
Open

libfabric-2.0: Completion changes (CQs and cntr) - Issue#9017 #26

syskovprdap opened this issue Nov 14, 2024 · 0 comments

Comments

@syskovprdap
Copy link
Contributor

ofiwg/libfabric#9017

  • No completion ordering guaranteed
  • Restrict a standard endpoint to a single CQ. Separate CQ for sends and receives no longer supported.
  • Scalable endpoints still support separate CQs. Technically, an app can create a scalable endpoint with 1 Tx and 1 Rx context and achieve the same behavior they have today. From the viewpoint of the provider, it can optimize for a different threading model under the proposed FI_THREAD changes.
  • Open question: A standard endpoint can have up to 4 counters attached. Can that be limited to 1, possible for RMA only?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@syskovprdap