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

08 of 10 LNX series - Add the FI_PEER to the SHM capabilities #10032

Conversation

amirshehataornl
Copy link
Contributor

Add the FI_PEER capability bit to SHM

Signed-off-by: Amir Shehata [email protected]

@amirshehataornl amirshehataornl force-pushed the 07_lnx_series_shm_fi_peer_bit branch 2 times, most recently from a920bb6 to 5975ade Compare May 10, 2024 00:33
When checking fabric attributes with ofi_check_fabric_attr() make sure to
consider provider exclusion.

When checking to see if a provider name is given, only consider ones which
are not excluded using the '^' character.

Signed-off-by: Amir Shehata <[email protected]>
It is not efficient to do a reverse lookup on the AV table when a message
is received. Some providers do not store the fi_addr_t associated with the
peer in the header passed on the wire. And it is not practical to require
providers to add that to wire header, as it would break backwards
compatibility.

In order to handle this case, an address matching callback is added to the
peer_srx.peer_ops structure. This allows the provider receiving the
message to register an address matching callback. This callback is called
by the owner provider to match an fi_addr_t with provider specific address
in the message received.

The callback allows the receiving provider to do an O(1) index into the AV
table to lookup the address of the peer, and then compare that with the
source address in the received message.

As part of this change provider specific address information needs to be
passed to the owner provider, which the owner will need to give back to the
receiving provider, when it attempts to do address matching.

Update the SHM and LINKx providers to conform with the API changes

Signed-off-by: Amir Shehata <[email protected]>
Add a new structure fi_peer_match to collect the parameters which need
to be passed to the get_msg and get_tag functions.

Update the util_get_tag() and util_get_msg() function callbacks.
Compilation gives a warning but not failing. This causes memory
corruption when the callbacks are called.

Signed-off-by: Amir Shehata <[email protected]>
@amirshehataornl amirshehataornl force-pushed the 07_lnx_series_shm_fi_peer_bit branch from 5975ade to 07d915b Compare May 16, 2024 13:23
Add a memory registration callback to the fi_ops_srx_peer. This allows
core providers to expose a memory registration callback which the parent
or peer provider can use to register memory on the receive path.

For example the CXI provider registers memory with the NIC on the receive
path. When using the peer infrastructure this can not happen because we
do not know which provider will perform the receive operation. But if
the source NID is specified then we can know and therefore we can
perform the receive buffer registration at the top of the receive path.

Signed-off-by: Amir Shehata <[email protected]>
Add FI_PEER capability bit

Signed-off-by: Amir Shehata <[email protected]>
The parent provider should be able to get access to the peer provider
callbacks. Added the srx block in the fid.context so we can retrieve it
later on.

Signed-off-by: Amir Shehata <[email protected]>
Add the FI_PEER capability bit to the SHM fi_infos

Signed-off-by: Amir Shehata <[email protected]>
@amirshehataornl amirshehataornl force-pushed the 07_lnx_series_shm_fi_peer_bit branch from 07d915b to 54bbd87 Compare May 16, 2024 13:40
@amirshehataornl amirshehataornl changed the title 07 lnx series shm fi peer bit 07 of 09 LNX series - Add the FI_PEER to the SHM capabilities May 16, 2024
@amirshehataornl amirshehataornl changed the title 07 of 09 LNX series - Add the FI_PEER to the SHM capabilities 08 of 10 LNX series - Add the FI_PEER to the SHM capabilities May 16, 2024
@j-xiong j-xiong closed this Aug 6, 2024
@j-xiong j-xiong reopened this Aug 6, 2024
@j-xiong j-xiong closed this Aug 6, 2024
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.

2 participants