EJFAT

From epsciwiki
Revision as of 20:04, 8 October 2021 by Goodrich (talk | contribs) (Created page with " This collaboration between '''E'''Snet and '''J'''Lab for '''F'''PGA '''A'''ccelerated '''T'''ransport (EJFAT) seeks a network data transport capability to aggregate an...")
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

This collaboration between ESnet and JLab for FPGA Accelerated Transport (EJFAT) seeks a network data transport capability to aggregate and dynamically route selected UDP traffic with endpoint feedback.

EJFAT will add meta-data to UDP data streams to be used both by the intervening FPGA, acting as a work Load Balancer (LB), to aggregate data packets from multiple logical input streams and dynamically route to endpoints and for an endpoint Reassembly Engine (RE) to perform custom reassembly resulting from network equipment fragmentation.

While the aggregation and routing meta-data included as the header in the payload is generic in design, it is being first utilized for streamed (non-triggered) data from the JLab DAQ to the back-end compute farm.


In the initial JLab deployment context, the FPGA will time-stamp aggregate across detector Data Acquisition System (DAQ) channels for the purpose of load balancing work to individual compute farm destinations in a farm status aware manner (see Figure \ref{fig:ejfat} in Appendix \ref{appendix:ejfat}), where work here is concerned with using data from an individual time-stamp across all DAQ channels to identify or reconstruct detector events.

This load balancing of computational work is under direct control of the compute farm via dynamic management of routing information communicated to the FPGA host CPU which is passed on to the FPGA.

As the aggregated/routed data is opaque to this design, it should be reusable for other data streams with aggregation/routing needs.