Lines Matching full:decompression

17 <li><a href="#Chapter7">Streaming Decompression Functions</a></li>
28   The LZ4 compression library provides in-memory compression and decompression functions.
37   Exact metadata depends on exact decompression function.
152         the receiving decompression function should provide
224   The same dictionary will have to be loaded on decompression side for successful decoding.
267 <a name="Chapter7"></a><h2>Streaming Decompression Functions</h2><pre>  Bufferless synchronous API
272 </b><p>  creation / destruction of streaming decompression tracking context.
279   Use this function to start decompression of a new stream of blocks.
281 …Dictionary is presumed stable : it must remain accessible and unmodified during next decompression.
292   When setting such a ring buffer for streaming decompression,
301 </b><p>  These decoding functions allow decompression of consecutive blocks in "streaming" mode.
302   A block is an unsplittable entity, it must be presented entirely to a decompression function.
303   Decompression functions only accepts one block at a time.
307 …Special : if decompression side sets a ring buffer, it must respect one of the following condition…
308   - Decompression buffer size is _at least_ LZ4_decoderRingBufferSize(maxBlockSize).
313     Decompression buffer size is _exactly_ the same as compression buffer size,
317   - Decompression buffer is larger than encoding buffer, by a minimum of maxBlockSize more bytes.
322 …e the last 64KB of decoded data into a safe buffer where it can't be modified during decompression,
330   Dictionary is presumed stable : it must remain accessible and unmodified during decompression.
331   Performance tip : Decompression speed can be substantially increased
398  and decompression to start at beginning of the buffer.
406  This technique is more useful for decompression,
410  In-place decompression will work inside any buffer
501 </b><p>  information structure to track an LZ4 stream during decompression.