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

Correctly resolve UCX/UCX_MO dependencies #63

Open
artpol84 opened this issue Mar 19, 2025 · 0 comments
Open

Correctly resolve UCX/UCX_MO dependencies #63

artpol84 opened this issue Mar 19, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@artpol84
Copy link
Contributor

With the introduction of Multi-Object (MO) UCX backend (PR #58) that depends on UCX backend we need to make sure the dependency is properly handled for all static/dynamic plugin configurations.

Initial thoughts to consider:

  • UCX is a plugin => UCX MO is a plugin and it just includes the code from UCX backend and not have plugin-to-plugin dependency
  • UCX is static => 2 options
    • UCX_MO has to be static as well
    • UCX_MO can be whatever, but if it's a plugin:
      • Either it relies on libnixl for UCX backend functionality
      • OR we build UCX_MO plugin so such that UCX symbols are not conflicting with UCX backend code that is part of libnixl. This would require some investigation
@mkhazraee mkhazraee added the enhancement New feature or request label Mar 21, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants