Skip to content

Conversation

aingerson
Copy link
Contributor

@aingerson aingerson commented Sep 2, 2025

A few things were missing to support running lnx with fabtests by default:

  • fabtests was by default requesting AV_MAP if the provider returned UNSPEC which lnx wasn't handling properly (we should fix the handling in lnx too but fabtests shouldn't be using AV_MAP anymore because it was deprecated)
  • lnx was missing a wait object implementation for internal util eq implementation
  • lnx was incorrectly erroring out for multiple iovs even though it does support it now
  • lnx was passing in the wrong protocol to the core providers and causing an initialization error
  • lnx doesn't support a lot of features - added exclude file to be able to run it with runfabtests with proper exclusion of invalid tests and documentation of limitations and issues
  • added lnx config file to run ubertest

AV_MAP was deprecated, default to AV_TABLE

Signed-off-by: Alexia Ingerson <[email protected]>
lnx uses eq_create to create an eq which calls the fabric wait object open function.
Since that's not implemented, opening an eq returns ENOSYS.

Add the util wait object implementation

This lets the user open an EQ (like in fabtests) but this EQ is currently never
used

Signed-off-by: Alexia Ingerson <[email protected]>
@aingerson aingerson force-pushed the main branch 2 times, most recently from 1737ebb to 5bf405b Compare September 3, 2025 16:06
lnx supports iov counts, it just has to be the minimum of all the providers
it supports (and less than the global LNX limit).
Remove failures for fewer than 1 iov

Signed-off-by: Alexia Ingerson <[email protected]>
lnx has to overwrite some of the hints passed into the main getinfo call
because they won't be valid for all core providers (for example the
remote comm/local comm specification). This also includes the fabric and
domain names which won't match the core providers.

The protocol setting was missing so if the provider passed in FI_PROTO_LNX,
it would fail the core getinfos because of a mismatch. This resets the protocol
to a value which won't fail any core providers (FI_PROTO_UNSPEC)

Signed-off-by: Alexia Ingerson <[email protected]>
@aingerson
Copy link
Contributor Author

Verified these changes work when enabling lnx fabtests in our CI which will come later.
All of this can wait until after the release

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.

1 participant