1. A. KlugeFeb 18, 2015 CRU form factor discussion & HLT FPGA processor part II A.Kluge, Feb 18, 2015 1

2. A. KlugeFeb 18, 2015 Outline Summary of 13 Jan’15 - CRU meeting https://indico.cern.ch/event/356712/ Summary of 4 Feb’15 – CRU-TPC meeting https://indico.cern.ch/event/369947/ 2

3. A. KlugeFeb 18, 2015 LTU TTS-GBT & busy On-detector electronics CRU Trigger & busy distribution FPGA proc. CRU CRU system with TTS link to CRU CRU.. common read-out unit O 2.. Online and Offline Computing System DCS.. Detector Control System TTS.. Trigger and Timing Distribution System CTP.. Central Trigger Processor LTU.. Local Trigger Unit GBT.. Gigabit Transceiver front-end links (GBT) →data & ←trigger & ←configuration DDL3 →data & ←configuration FLP CTPTrig. Dist. ATCA or PCI

4. A. KlugeFeb 18, 2015 LTU On-detector electronics CRU Trigger & busy distribution FPGA proc. CRU FLP CTPTrig. Dist. ATCA 9 link TTS links 9 ATCA crates only for all ALICE read-out for 324 24-channel CRU cards ATCA is not made for use in radiation nor magnetic field but could be adapted  TRD 2500 DDL3 Computer purchase, maintenance independent of CRU FPGA processes might run in CRU making FPGA proc. unnecessary

5. A. KlugeFeb 18, 2015 LTU On-detector electronics CRU Trigger & busy distribution FPGA proc. CRU FLP CTPTrig. Dist. PCIe 324 link TTS links 324 24-channel CRU cards are mounted in 324 FLPs PCs are not made for use in radiation nor magnetic field and would not be adapted  TRD fibers need to to surface 0 DDL3 Computer purchase, maintenance dependent on CRU FPGA processes might run in CRU making FPGA proc. unnecessary Trig. Dist. could be done by 2 levels of CRU-PCI cards 1  14 – 14  324 => 15 * CRU-PCI

6. A. KlugeFeb 18, 2015 Introduction read-out & O2 from TDR  2 basic choices: ATCA – PCIe CRU-ATCA independent from O2 in terms of installation, development and future maintenance development not followed by LHCb present version solid, no external memory, but implementation possible 2500 physical DDL3 needed, trigger distribution very simple (9 links) more expensive TRD might not need to extend fibers CRU-PCI dependent on O2-FLP infrastructure development can be done in collaboration with LHCb presently in layout phase no external memory memory in principle feasible, but not implemented for LHCb no physical DDL3 needed, some 350 TTS trigger links needed cheaper PCIe slot needs to exist for PC upgrades TRD needs to extend fibers 6

7. A. KlugeFeb 18, 2015 AMC40/PCI40 (J.P. Chachemiche) AMC40 fully tested for LHCb needs ATCA mother card: only two were made PCI40 in layout stage change to PCI40 in order to profit from PC processor memory  no memory on PCI40 board PCI40 can profit from better performing power supply/cooling  higher FPGA processor performance Advice: develop FPGA firmware before hardware is chosen 7

8. A. KlugeFeb 18, 2015 Performance of cluster finder (T. Alt/H. Engel) Processing performance in FPGA processor is by far higher than in CPU (750 Xeon E5 core = 1 FPGA)  move cluster finder in FPGA processor 30 cluster finders fit in one modern FPGA Use high level languages Consider commercial developments 8

9. A. KlugeFeb 18, 2015 CRU for ALICE TPC (C. Lippmann) Pad ordering is memory demanding (neither AMC40 nor PCI40 has external memory) TPC needs to assess the amount of memory needed (the need to add hardware memory on AMC40/PCI40 might arise) 9

10. A. KlugeFeb 18, 2015 CRU Summary Argument towards PCI40 is performance in FPGA due to better power supply/cooling Common solution between LHCb & ALICE is an important plus Modification of PCI40 for ALICE might be needed if we need PCI40 with memory Commercial solution is of interest if there were a large supplier with solution fulfilling requirements and long term support 10

11. A. KlugeFeb 18, 2015 CRU Summary Proposal Limited time available prototype required in 2016  move base line to PCI40 (O2 believes the risk is acceptable)  O2/HLT studies processing needs  TPC studies processing/memory needs  verify (O2/TPC) whether additional FPGA processor can be suppressed  at the same time we have open the possibility of commercial production of PCI40 or equivalent 11

12. A. KlugeFeb 18, 2015 PCI hardware implementation options 4 options PCI40 PCI40 with memory PCI40 + FPGA processor commercial TPC needs to find out whether it can be implemented in FPGA any possible hardware modification needs to be done from now on Ken Oyama starts working on this topic 12

13. A. KlugeFeb 18, 2015 Summary CRU baseline PCI40 development program is dependent on TPC needs input from TPC is needed 13