Add host-IB zero-copy transport + per-peer mapper cache#2736
Open
Regina8023 wants to merge 1 commit into
Open
Conversation
Summary:
Introduce the host-side IB P2P transport stack, end-to-end for the
pure zero-copy (ZC) mode. This is the first of two diffs; the
copy-based (CB) mode lands in a follow-up.
What's in this diff:
- ctran::transport::IP2pHostTransport — backend-neutral abstract
interface algorithms see. Carries pure ctrl-msg primitives
(iSendCtrl/iRecvCtrl take raw void* payloads + size) and
mode-agnostic SendChunkArgs / RecvChunkArgs.
- ctran::transport::ib::HostZcTransport — pure-ZC concrete impl. No
staging buffers, no state machine. iSendChunk is a thin wrapper
on vcs_[vcIdx]->iput; iRecvChunk bumps per-VC notify counters.
- ctran::transport::ib::impl — shared ctrl-plane helpers
(ensureVcsReady, iSendCtrlImpl, iRecvCtrlImpl, testCtrlDoneImpl,
waitCtrlDoneImpl, progressImpl, exportRecvBuf, importRemoteInfo,
toIbRegElem, CtrlRequestPriv friend struct).
- CtranMapper::getP2pTransport(peer, mode) per-peer cache. The
kCopyBased branch is a temporary FB_CHECKABORT pointing at the
follow-up diff.
- MockP2pHostTransport.h for unit-testing algos against the
interface.
- ctran_mapper_host_transport_ut: cache lifecycle + per-peer
caching tests (ZC scope).
- host_transport_dist_ut: end-to-end ZC RoundTrip +
BidirectionalRoundTrip across {1, 2, 4} channels on real IB.
- HostTransportDesign.md: full architecture doc describing both ZC
and CB. CB sections describe the API + state machine the
follow-up diff implements.
Reviewed By: minsii
Differential Revision: D106138307
Contributor
|
@Regina8023 has exported this pull request. If you are a Meta employee, you can view the originating Diff in D106138307. |
This file contains hidden or 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
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.
Summary:
Introduce the host-side IB P2P transport stack, end-to-end for the
pure zero-copy (ZC) mode. This is the first of two diffs; the
copy-based (CB) mode lands in a follow-up.
What's in this diff:
interface algorithms see. Carries pure ctrl-msg primitives
(iSendCtrl/iRecvCtrl take raw void* payloads + size) and
mode-agnostic SendChunkArgs / RecvChunkArgs.
staging buffers, no state machine. iSendChunk is a thin wrapper
on vcs_[vcIdx]->iput; iRecvChunk bumps per-VC notify counters.
(ensureVcsReady, iSendCtrlImpl, iRecvCtrlImpl, testCtrlDoneImpl,
waitCtrlDoneImpl, progressImpl, exportRecvBuf, importRemoteInfo,
toIbRegElem, CtrlRequestPriv friend struct).
kCopyBased branch is a temporary FB_CHECKABORT pointing at the
follow-up diff.
interface.
caching tests (ZC scope).
BidirectionalRoundTrip across {1, 2, 4} channels on real IB.
and CB. CB sections describe the API + state machine the
follow-up diff implements.
Reviewed By: minsii
Differential Revision: D106138307