Lines Matching refs:compression
7 The compression framework provides a generic set of APIs to perform compression services
8 as well as to query and configure compression devices both physical(hardware) and virtual(software)
9 to perform those services. The framework currently only supports lossless compression schemes:
18 Physical compression devices are discovered during the bus probe of the EAL function
21 Specific physical compression devices, like other physical devices in DPDK can be
35 * If DPDK application requires multiple software compression PMD devices then required
38 * An Application with multiple compression device instances exposed by the same PMD must
49 All virtual compression devices support the following initialization parameters:
59 - A unique device index used to designate the compression device in all functions
62 - A device name used to designate the compression device in console messages, for
68 The configuration of each compression device includes the following operations:
74 The ``rte_compressdev_configure`` API is used to configure a compression device.
84 Each compression device queue pair is individually configured through the
99 context for enqueuing operations or dequeuing operations on the same compression device
102 core on which it was enqueued. This means that a compression burst enqueue/dequeue
112 acceleration and CPU features. List of compression device features can be seen in the
116 such as a stateful compression/decompression, checksums operation etc. List of algorithm
145 DPDK compression supports two types of compression methodologies:
147 - Stateless, data associated to a compression operation is compressed without any reference
148 to another compression operation.
150 - Stateful, data in each compression operation is compressed with reference to previous compression
169 by the compression PMD to process the requested operation.
175 The compressdev library provides an API set for managing compression operations which
177 that the compression operation is interleaved optimally across the channels and
183 compression operations from a given compression operation mempool.
264 to specify the details of the compression operation such as algorithm,
271 alongside compression and decompression of data. A PMD reflects its
274 before compression and after decompression.
295 (required only on compression side),
332 * pseudocode for stateless compression
363 /* create priv_xform and initialize it for the compression device. */
378 /* prepare ops for compression operations */
428 A Stateful operation in DPDK compression means application invokes enqueue
447 `stream` in DPDK compression is a logical entity which identifies related set of ops, say, a one la…
449 represented by compression op `rte_comp_op`. Whenever application wants a stateful processing of su…
453 requires previous op data for compression/decompression. A PMD allocates and set up resources such
475 * pseudocode for stateful compression
513 /* Prepare source and destination mbufs for compression operations */
573 Burst in compression API
576 Scheduling of compression operations on DPDK's application data path is
577 performed using a burst oriented asynchronous API set. A queue pair on a compression
578 device accepts a burst of compression operations using enqueue burst API. On physical
581 operations is usually completed during the enqueue call to the compression
583 from the queue pair on the compression device, from physical devices this is usually
588 A burst in DPDK compression can be a combination of stateless and stateful operations with a condit…
614 The burst enqueue API uses a compression device identifier and a queue pair
615 identifier to specify the compression device queue pair to schedule the processing on.