From: Sameer Vaze <svaze@qti.qualcomm.com>
To: Fan Zhang <fanzhang.oss@gmail.com>, Ashish Gupta <ashishg@marvell.com>
Cc: dev@dpdk.org, Sameer Vaze <svaze@qti.qualcomm.com>
Subject: [PATCH v2 1/3] compressdev: support for dictionaries and PDCP checksum
Date: Fri, 19 Sep 2025 14:48:27 -0600 [thread overview]
Message-ID: <20250919204827.2662199-1-svaze@qti.qualcomm.com> (raw)
In-Reply-To: <20250919184821.2567839-1-svaze@qti.qualcomm.com>
Adds definitions for PDCP checksums and apis to pass in
dictionaries
Signed-off-by: Sameer Vaze <svaze@qti.qualcomm.com>
---
lib/compressdev/rte_comp.h | 31 +++++++++++++++++++++++++++++++
1 file changed, 31 insertions(+)
diff --git a/lib/compressdev/rte_comp.h b/lib/compressdev/rte_comp.h
index 96d9b276dd..169d3d960e 100644
--- a/lib/compressdev/rte_comp.h
+++ b/lib/compressdev/rte_comp.h
@@ -101,6 +101,10 @@ enum rte_comp_op_status {
* is not an error case. Output data up to op.produced can be used and
* next op in the stream should continue on from op.consumed+1.
*/
+ RTE_COMP_OP_STATUS_CHECK_SUM_VALIDATION_FAILED,
+ /**< Checksum validation failed. Either calculated does checksum not match
+ * the one provided or there was an error calculating the checksum
+ */
};
/** Compression Algorithms */
@@ -166,6 +170,10 @@ enum rte_comp_checksum_type {
/**< Generates a xxHash-32 checksum, as used by LZ4.
* https://github.com/Cyan4973/xxHash/blob/dev/doc/xxhash_spec.md
*/
+ RTE_COMP_CHECKSUM_3GPP_PDCP_UDC,
+ /**< Generates checksum as defined under Uplink Data Compression
+ * checksum as defined in the 3GPP PDCP specification
+ */
};
/** Compression Huffman Type - used by DEFLATE algorithm */
@@ -201,6 +209,11 @@ enum rte_comp_flush_flag {
*/
};
+#define DEFLATE_MAX_WINDOW_SIZE (1ULL << 15)
+
+#define DEFLATE_MIN_WINDOW_SIZE (1ULL << 8)
+
+
/** Compression transform types */
enum rte_comp_xform_type {
RTE_COMP_COMPRESS,
@@ -305,6 +318,15 @@ struct rte_comp_compress_xform {
/**< Hash algorithm to be used with compress operation. Hash is always
* done on plaintext.
*/
+ uint8_t *dictionary;
+ /**<
+ * Pointer to memory containing dictionary to be used for inflate
+ * and deflate operations
+ */
+ uint16_t dictionary_len;
+ /**<
+ * Length of dictionary to be used
+ */
};
/**
@@ -328,6 +350,15 @@ struct rte_comp_decompress_xform {
/**< Hash algorithm to be used with decompress operation. Hash is always
* done on plaintext.
*/
+ uint8_t *dictionary;
+ /**<
+ * Pointer to memory containing dictionary to be used for inflate
+ * and deflate operations
+ */
+ uint16_t dictionary_len;
+ /**<
+ * Length of dictionary to be used
+ */
};
/**
--
2.31.1
prev parent reply other threads:[~2025-09-19 20:48 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-19 18:48 [PATCH " Sameer Vaze
2025-09-19 18:48 ` [PATCH 2/3] compress/zlib: " Sameer Vaze
2025-09-19 20:49 ` [PATCH v2 " Sameer Vaze
2025-09-19 18:48 ` [PATCH 3/3] app/compress-perf: " Sameer Vaze
2025-09-19 20:49 ` [PATCH v2 " Sameer Vaze
2025-09-19 20:48 ` Sameer Vaze [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20250919204827.2662199-1-svaze@qti.qualcomm.com \
--to=svaze@qti.qualcomm.com \
--cc=ashishg@marvell.com \
--cc=dev@dpdk.org \
--cc=fanzhang.oss@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).