[Sbs_daq] Big endian raw data?
    Ole Hansen 
    ole at jlab.org
       
    Sun Oct  3 13:00:33 EDT 2021
    
    
  
Hi guys,
Bradley reported a crash of the replay (actually in EVIO) with 
/adaq1/data1/sbs/grinch_72.evio.0 (see 
https://logbooks.jlab.org/entry/3916105).
When digging into the cause of this crash, I discovered that these raw 
data are written in big-endian format. How can this be? I thought the 
front-ends are Intel processors. Are we taking data with ARM chips that 
are configured for big-endian mode? Is this a mistake, or is there some 
plan to it?
These big-endian data have to be byte-swapped when processing them on 
x86, which is what all our compute nodes run. That's a LOT of work. It 
leads to significant and seemingly completely unnecessary overhead. I.e. 
we're burning CPU cycles for nothing good, it seems.
Please explain.
Ole
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://mailman.jlab.org/pipermail/sbs_daq/attachments/20211003/b7d54daf/attachment.html>
    
    
More information about the Sbs_daq
mailing list