Lines Matching full:decompression

53   The LZ4 compression library provides in-memory compression and decompression functions.
62   Exact metadata depends on exact decompression function.
224  *        the receiving decompression function should provide
304  *  The same dictionary will have to be loaded on decompression side for successful decoding.
349 *  Streaming Decompression Functions
355  *  creation / destruction of streaming decompression tracking context.
363  *  Use this function to start decompression of a new stream of blocks.
365 …Dictionary is presumed stable : it must remain accessible and unmodified during next decompression.
375  *  When setting such a ring buffer for streaming decompression,
385  *  These decoding functions allow decompression of consecutive blocks in "streaming" mode.
386  *  A block is an unsplittable entity, it must be presented entirely to a decompression function.
387  *  Decompression functions only accepts one block at a time.
391 …*  Special : if decompression side sets a ring buffer, it must respect one of the following condit…
392  *  - Decompression buffer size is _at least_ LZ4_decoderRingBufferSize(maxBlockSize).
397  *    Decompression buffer size is _exactly_ the same as compression buffer size,
401  *  - Decompression buffer is larger than encoding buffer, by a minimum of maxBlockSize more bytes.
406 …e the last 64KB of decoded data into a safe buffer where it can't be modified during decompression,
416  *  Dictionary is presumed stable : it must remain accessible and unmodified during decompression.
417  *  Performance tip : Decompression speed can be substantially increased
502 /*! In-place compression and decompression
507  * and decompression to start at beginning of the buffer.
515  * This technique is more useful for decompression,
519  * In-place decompression will work inside any buffer
649  *  information structure to track an LZ4 stream during decompression.
704 /*! Obsolete decompression functions (since v1.8.0) */