mis-match between the doc and data in test

[nono0210]

I am not sure if my understanding is correct.
I have checked the data in the gzip.inbound, and the head data are
0x400000000a000400 SoT 0xff
0x0000000000000000 EoT 0xff
0x800000000a000601 SoT 0xff
0x000000000580f000 0xff
0x3a00000000000450 EoT 0xff
0x800000000a000d0f SoT 0xff

i can see from the waveform they are mapping to RQE, CMD,AUX FRMD part but each field i can hardly aligned as 3.1.2.9 comp_ctrl (Offset:0x10[31:0], Size: 32) have field algorithm, but i cannot find the data above 0x3a00000000000450 can mapped to gzip algo ..
also in the spec the define Length of the TLV in units of 4 bytes. This length is computed over the entirety of the TLV Type, Length and data fields are the same description for each header part in the Top_Micro_Architeture spec .
Are there any updated spec and is there plan for this IP roadmap?

thanks

[michaelgmcintyre]

Hi nono0210,

The purpose of the Open Source release is both for educational purposes and as a baseline for design reuse.

From the educational perspective, the release of all the collateral, design specifications, microarchitecture specifications, and RTL, as a contribution to the Open Source community provides our insight and approach to solving a growing issue with cloud computing - how to maximize storage via a lossless compression algorithm/implementation of data at real-time line rates. As the implementation is complete we are not planning to revise any of the specifications.

From the design reuse perspective, it provides all the RTL we developed during the multi-year Corsica ASIC program (https://azure.microsoft.com/en-us/blog/improved-cloud-service-performance-through-asic-acceleration/). This represents a significant amount of research, architectural design, implementation, and verification. We've Open Sourced all of it! We built it using a specific ASIC tool flow (Synopsis) with the hope that others will be able to find utility in it.

Thanks,
Michael