DPDK patches and discussions
 help / color / mirror / Atom feed
From: Akhil Goyal <gakhil@marvell.com>
To: Sameer Vaze <svaze@qti.qualcomm.com>,
	Fan Zhang <fanzhang.oss@gmail.com>,
	 Ashish Gupta <ashishg@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [EXTERNAL] [PATCH 1/3] compressdev: support for dictionaries and PDCP checksum
Date: Tue, 30 Sep 2025 20:03:06 +0000	[thread overview]
Message-ID: <CO6PR18MB4484EEAC621E731A4E5E64C8D81AA@CO6PR18MB4484.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20250924161918.2211290-1-svaze@qti.qualcomm.com>

Hi Sameer,
> Adds definitions for PDCP checksums and apis to pass in
> dictionaries
I think you need to define new algo UDC as well.

> 
> Signed-off-by: Sameer Vaze <svaze@qti.qualcomm.com>

Please update version in the patch title while sending the new version.
It took me a lot of time to figure out which version I should review and reply to.
I can see there are 10s of series spammed without updating the version.
Please take care of this while sending the next version.
Also add in-reply-to tag of previous version while sending next version.
Please check https://doc.dpdk.org/guides/contributing/patches.html#sending-patches
https://doc.dpdk.org/guides/contributing/patches.html#the-review-process

> ---
And you should also specify change log here after ---

>  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://urldefense.proofpoint.com/v2/url?u=https-
> 3A__github.com_Cyan4973_xxHash_blob_dev_doc_xxhash-
> 5Fspec.md&d=DwIDAg&c=nKjWec2b6R0mOyPaz7xtfQ&r=DnL7Si2wl_PRwpZ9TW
> ey3eu68gBzn7DkPwuqhd6WNyo&m=YLWffSHu_HeEi63ZTpMIS7uCsbTGlu1gZDDe
> Pxv8nL7v3JAvIdKcNrrUq3BR5Y22&s=b5bCLrPbUjjxy1ItxfYQOUoHAnDjqjVwVfh6il
> TDCIw&e=
>  	 */
> +	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)
Wrong namespace used.
Are these really required to be defined here.
I do see any comments where these macros will be used and what is the use case.

> +
Remove extra line here

> +#define	DEFLATE_MIN_WINDOW_SIZE		(1ULL << 8)
> +
Remove extra line here
> +
>  /** 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
> +	 */

Don’t you need to define UDC in rte_comp_algorithm?
And move these algorithm specific fields into a separate struct and add that into the union defined above in this struct?
Seems patch is incomplete.

There is no update to documentation as well.
doc/guides/prog_guide/compressdev.rst
doc/guides/compressdevs/features/default.ini

>  };
> 
>  /**
> @@ -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
> +	 */
Please make this in a single line if it is under 100 characters.

> +	uint16_t dictionary_len;
> +	/**<
> +	 * Length of dictionary to be used
> +	 */
Make this also in a single line instead of 3 lines as being followed for other fields.


>  };
> 
>  /**
> --
> 2.31.1


      parent reply	other threads:[~2025-09-30 20:03 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-24 16:19 Sameer Vaze
2025-09-24 16:19 ` [PATCH 2/3] compress/zlib: " Sameer Vaze
2025-09-24 16:19 ` [PATCH 3/3] app/compress-perf: " Sameer Vaze
2025-09-24 20:24 ` [PATCH 1/3] compressdev: " Patrick Robb
2025-09-26 16:15   ` Sameer Vaze
2025-09-26 20:50     ` Patrick Robb
2025-09-26 20:51       ` Patrick Robb
2025-09-30 20:03 ` Akhil Goyal [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=CO6PR18MB4484EEAC621E731A4E5E64C8D81AA@CO6PR18MB4484.namprd18.prod.outlook.com \
    --to=gakhil@marvell.com \
    --cc=ashishg@marvell.com \
    --cc=dev@dpdk.org \
    --cc=fanzhang.oss@gmail.com \
    --cc=svaze@qti.qualcomm.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).