| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
Before this change, introducing a new collective algorithm required touching
multiple files. CollectiveParams setup was in common_runtime/collective_param_resolver_local,
and the data movement was in common_runtime/reducer and common_runtime/broadcaster.
This change introduces CollectiveImplementationInterface.
CollectiveImplementationInterface brings together param initialization and data
movement for a collective algorithm. Every collective implementation will
implement this interface and override the virtual methods. This should
hopefully reduce obscurity and lead to code with fewer dependencies.
PiperOrigin-RevId: 210430157
|
| |
|
|
|
|
|
|
|
|
| |
Add Broadcaster.
A few minor adjustments to CollectiveParams and RMA.
This change is part of a series of changes introducing infrastructure
for collective ops and initial implementations of reduction and broadcast.
PiperOrigin-RevId: 193562391
|
|
|
The basic interface definitions, local-only versions of remote-access,
param-resolution, device-resolution and mgr.
A collective op is able to execute synchronously across devices
and across separate graphs. Collective ops to be introduced eventually
include broadcast and all-reduce. This change is part of a series of
changes that will introduce the necessary infrastructure then the
initial op implementations.
PiperOrigin-RevId: 190860248
|
Ayush Dubey
A. Unique TensorFlower