I have been reworking compression API implementation to properly
allocate/deallocate memory. Right now I've stumbled upon digest part of
compression API. Currently on both compression and decompression digest
should be written after co/decompressed output data. However both our
hardware and current DPDK compressdev use out-of-band data to pass
resulting hash. Do we want to stick with in-package data or do we want
to switch to OOB way to return message digest?

With best wishes

Reply via email to