DPDK patches and discussions
 help / color / mirror / Atom feed
From: Raja Zidane <rzidane@nvidia.com>
To: <dev@dpdk.org>
Subject: [dpdk-dev] [PATCH 0/2] fix level configuration in compress
Date: Tue, 26 Oct 2021 01:52:40 +0000	[thread overview]
Message-ID: <20211026015242.21156-1-rzidane@nvidia.com> (raw)

The mlx5 compress PMD uses HW acceleration for the compress operations.
The mlx5 HW device has no level style mode, which does a tradeoff between
throughput and compression ratio, unlike SW drivers where the CPU is doing
the compress, and more CPU effort can cause a better compression ratio.
The mlx5 driver wrongly defined the Huffman block size configuration
according to the level that doesn't fill the level API requirement for
the tradeoff.

Remove the effect of the level configuration in compress operation. 
Add "log-block-size" devarg to select compression block size manually.

Raja Zidane (2):
  compress/mlx5: fix level configuration in compress
  compress/mlx5: add block size devarg

 doc/guides/compressdevs/mlx5.rst       | 10 ++++
 doc/guides/rel_notes/release_21_11.rst |  2 +
 drivers/compress/mlx5/mlx5_compress.c  | 79 +++++++++++++++++++++-----
 3 files changed, 76 insertions(+), 15 deletions(-)

-- 
2.17.1


             reply	other threads:[~2021-10-26  1:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-26  1:52 Raja Zidane [this message]
2021-10-26  1:52 ` [dpdk-dev] [PATCH 1/2] compress/mlx5: " Raja Zidane
2021-10-26  1:52 ` [dpdk-dev] [PATCH 2/2] compress/mlx5: add block size devarg Raja Zidane
2021-10-31 19:49 ` [dpdk-dev] [EXT] [PATCH 0/2] fix level configuration in compress 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=20211026015242.21156-1-rzidane@nvidia.com \
    --to=rzidane@nvidia.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).