1 / 7

ODR Status 29 July 2008 Matt Warren Valeria Bartsch, Barry Green, Andrzej Miesijuk, Tao Wu

ODR Status 29 July 2008 Matt Warren Valeria Bartsch, Barry Green, Andrzej Miesijuk, Tao Wu. Hardware/Firmware. ODR is working(!) Receive data on 4x fibre (RX), Write to disk FAST (250MB) Send data up fibre (TX) Controlled from Linux driver Future upgrade: Decode event header from LDA

giona
Download Presentation

ODR Status 29 July 2008 Matt Warren Valeria Bartsch, Barry Green, Andrzej Miesijuk, Tao Wu

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ODR Status29 July 2008Matt WarrenValeria Bartsch, Barry Green, Andrzej Miesijuk, Tao Wu

  2. Hardware/Firmware • ODR is working(!) • Receive data on 4x fibre (RX), • Write to disk FAST (250MB) • Send data up fibre (TX) • Controlled from Linux driver • Future upgrade: Decode event header from LDA • Provides on-line info • Can deal with control messages from LDA • Allows host to write to disk without processing Matt Warren & Co. - ODR Starus

  3. Software Status ODR receiver: program running on a host machine. Communicate with ODR cards,retrieves the data, sets up ODR card parameters. Progress in the following areas: • Data transferred from ODR memory -> host memory->to disk (rate 250 MB/s for event fragment 2 kB • Tested sending messages (Tx message to LDA) • Interface to DOOCS and processing messages: DOOCS->ODR receiver ->ODR, ODR receiver-> DOOCS: a) Setting up parameters: ODR Receiver and ODR card b) Passing ODR statistics back to DOOCS c) Passing commands to ODR receiver (start, stop,pause, etc)‏ Matt Warren & Co. - ODR Starus

  4. Performance (data to memory)‏ Improvements in performance when accessing more then one channel. The maximum performance achieved for 3-channels access. Adding additional Channel (4-channel access) does not yield improvement in transfer rate. Matt Warren & Co. - ODR Starus

  5. Performance Top:Data to memory All other: data to disk: a) best performance- scatter gather- data copied to up to 80 buffers, then written to disk. Two lower curves: data to a single memory buffer, then copied to disk. Single channel. Data written to RAID array. Maximum bandwidth for the array: 300 MB/s. Adding active channel has no effect on the rate (remain constant). Best performance for scatter-gather scenario. Matt Warren & Co. - ODR Starus

  6. Supervisor ODR VHDL code FIFO Dup. DOOCS Interface Data Buff Data Buff Data Buff Interface to DOOCs DOOCS TxLDA msg DMA FIFO to user buffer Two way communication Requester DMA data to user buffer(s)‏ (host memory)‏ From DOOCS perspective, everything to right of line is “ODR” Hardware ODR Matt Warren & Co. - ODR Starus

  7. Future Development • Improve DOOCS GUI. • Add (DOOCS) plots of basic ODR statistics ( on-line). • Create event fragment data base (inside DOOCS ?)‏ • Test connectivity to LDA with the “real” LDA hardware Matt Warren & Co. - ODR Starus

More Related