One RPCClient per Core #345
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
hunhoffe
commented
Nov 21, 2023
| )) | ||
| }; | ||
| let clients = | ||
| crate::transport::shmem::init_shmem_rpc(true).expect("Failed to initialize shmem RPC"); |
There was a problem hiding this comment.
We need to create ethernet instead of shmem when ethernet is selected
| .expect("Failed to create shmem transport"), | ||
| ); | ||
| let transports = | ||
| create_shmem_transport(mid.try_into().unwrap()).expect("Failed to create shmem transport"); |
There was a problem hiding this comment.
We need to use ethernet instead of shmem when ethernet is selected
…nization still required
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Previously, each client kernel only had 1 RPC client. Now, we are changing to one RPC client per core per client kernel.