From: "Zhang, Fan" <fanzhang.oss@gmail.com>
To: dev@dpdk.org
Subject: Re: [PATCH v3 0/4] compressdev: add LZ4 support
Date: Mon, 13 Feb 2023 15:47:14 +0000 [thread overview]
Message-ID: <91d6c361-3908-ba5c-2afc-3a1f81f929b6@gmail.com> (raw)
In-Reply-To: <20230213061140.2157499-1-michaelba@nvidia.com>
Hi,
The patchset only have library change and added performance tests.
We shall have at least one PMD to support the added algorithms and unit
test updated for the PMD/algorithms.
Regards,
Fan
On 2/13/2023 6:11 AM, Michael Baum wrote:
> Add support for LZ4 compression algorithm for both API and app.
>
> In addition, enable app to test de/comp only. This option already
> exists in both app doc and arguments but isn't implemented inside the
> application.
>
> LZ4: https://github.com/lz4/lz4
> RFC:
> https://patchwork.dpdk.org/project/dpdk/patch/20220410182622.8828-1-rzidane@nvidia.com/
>
> v2:
> - Add macros for all LZ4 flags in the standard.
> - Rebase.
>
> v3:
> - Rebase.
>
> Michael Baum (4):
> compressdev: add LZ4 algorithm support
> app/test-compress-perf: allow test single compress operation
> app/test-compress-perf: add algo option
> app/test-compress-perf: add LZ4 support
>
> app/test-compress-perf/comp_perf_options.h | 9 +-
> .../comp_perf_options_parse.c | 83 +++++++++++-
> .../comp_perf_test_common.c | 126 +++++++++++++-----
> .../comp_perf_test_cyclecount.c | 82 +++++++-----
> .../comp_perf_test_throughput.c | 75 +++++++----
> .../comp_perf_test_verify.c | 75 +++++++----
> app/test-compress-perf/main.c | 63 +++++++--
> doc/guides/compressdevs/features/default.ini | 7 +
> doc/guides/rel_notes/release_23_03.rst | 16 +++
> doc/guides/tools/comp_perf.rst | 5 +
> lib/compressdev/rte_comp.c | 12 ++
> lib/compressdev/rte_comp.h | 79 ++++++++++-
> 12 files changed, 488 insertions(+), 144 deletions(-)
>
next prev parent reply other threads:[~2023-02-13 15:47 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 7:45 [PATCH " Michael Baum
2023-01-09 7:45 ` [PATCH 1/4] compressdev: add LZ4 algorithm support Michael Baum
2023-01-30 18:35 ` [EXT] " Akhil Goyal
2023-01-30 20:36 ` Michael Baum
2023-01-31 6:29 ` Akhil Goyal
2023-01-09 7:45 ` [PATCH 2/4] app/test-compress-perf: allow test single compress operation Michael Baum
2023-01-09 7:45 ` [PATCH 3/4] app/test-compress-perf: add algo option Michael Baum
2023-01-09 7:45 ` [PATCH 4/4] app/test-compress-perf: add LZ4 support Michael Baum
2023-02-02 9:13 ` [PATCH v2 0/4] compressdev: " Michael Baum
2023-02-02 9:13 ` [PATCH v2 1/4] compressdev: add LZ4 algorithm support Michael Baum
2023-02-05 17:20 ` [EXT] " Akhil Goyal
2023-02-02 9:13 ` [PATCH v2 2/4] app/test-compress-perf: allow test single compress operation Michael Baum
2023-02-02 9:13 ` [PATCH v2 3/4] app/test-compress-perf: add algo option Michael Baum
2023-02-02 9:13 ` [PATCH v2 4/4] app/test-compress-perf: add LZ4 support Michael Baum
2023-02-13 6:11 ` [PATCH v3 0/4] compressdev: " Michael Baum
2023-02-13 6:11 ` [PATCH v3 1/4] compressdev: add LZ4 algorithm support Michael Baum
2023-02-13 6:11 ` [PATCH v3 2/4] app/test-compress-perf: allow test single compress operation Michael Baum
2023-02-13 7:23 ` [EXT] " Akhil Goyal
2023-02-14 16:37 ` Michael Baum
2023-02-13 6:11 ` [PATCH v3 3/4] app/test-compress-perf: add algo option Michael Baum
2023-02-13 7:29 ` [EXT] " Akhil Goyal
2023-02-14 16:32 ` Michael Baum
2023-02-13 6:11 ` [PATCH v3 4/4] app/test-compress-perf: add LZ4 support Michael Baum
2023-02-13 15:47 ` Zhang, Fan [this message]
2023-02-13 15:56 ` [PATCH v3 0/4] compressdev: " Michael Baum
2023-02-14 17:40 ` [PATCH v4 " Michael Baum
2023-02-14 17:40 ` [PATCH v4 1/4] compressdev: add LZ4 algorithm support Michael Baum
2023-02-14 17:40 ` [PATCH v4 2/4] app/test-compress-perf: fix some typos Michael Baum
2023-02-14 17:40 ` [PATCH v4 3/4] app/test-compress-perf: fix missing test single compress op Michael Baum
2023-02-14 17:40 ` [PATCH v4 4/4] app/test-compress-perf: add algo option Michael Baum
2023-02-16 8:01 ` [EXT] [PATCH v4 0/4] compressdev: add LZ4 support Akhil Goyal
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=91d6c361-3908-ba5c-2afc-3a1f81f929b6@gmail.com \
--to=fanzhang.oss@gmail.com \
--cc=dev@dpdk.org \
/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).