From: "Trahe, Fiona" <fiona.trahe@intel.com>
To: Matan Azrad <matan@nvidia.com>,
"ashish.gupta@marvell.com" <ashish.gupta@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
NBU-Contact-Thomas Monjalon <thomas@monjalon.net>,
"Trahe, Fiona" <fiona.trahe@intel.com>
Subject: Re: [dpdk-dev] DPDK compress API - questions
Date: Wed, 6 Jan 2021 16:05:43 +0000 [thread overview]
Message-ID: <BN7PR11MB28653F39A5A75A40D44CB191E4D00@BN7PR11MB2865.namprd11.prod.outlook.com> (raw)
In-Reply-To: <MW2PR12MB24921258A74E6545D9774A03DFD00@MW2PR12MB2492.namprd12.prod.outlook.com>
From: Matan Azrad <matan@nvidia.com>
Sent: Wednesday, January 6, 2021 3:57 PM
To: Trahe, Fiona <fiona.trahe@intel.com>; ashish.gupta@marvell.com
Cc: dev@dpdk.org; NBU-Contact-Thomas Monjalon <thomas@monjalon.net>
Subject: DPDK compress API - questions
Hi Fiona, Ashish
I'm going to add new HW offload compress PMD for mlx5 devices in 21.02.
I have some questions on the API:
#define RTE_COMP_FF_NONCOMPRESSED_BLOCKS (1ULL << 11)
/**< Creation of non-compressed blocks using RTE_COMP_LEVEL_NONE is supported */
1. What does it mean non-compressed block ? DMA?
[Fiona] Not exactly. E.g. for Deflate, if the output is non-compressed blocks, it still has the deflate headers.
So is not a direct DMA of the input data. As this may not be supported by all PMDs it is exposed in a feature flag.
2. Does Using RTE_COMP_LEVEL_NONE or RTE_COMP_ALGO_NULL the same?
[Fiona] No. ALGO_NULL would be DMA.
/**< No compression.
* Pass-through, data is copied unchanged from source buffer to
* destination buffer.
*/
LEVEL_NONE should output the data in the correct format for the specified algorithm.
Probably I will add more question later.
Thanks
Matan
prev parent reply other threads:[~2021-01-06 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-06 15:57 Matan Azrad
2021-01-06 16:05 ` Trahe, Fiona [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=BN7PR11MB28653F39A5A75A40D44CB191E4D00@BN7PR11MB2865.namprd11.prod.outlook.com \
--to=fiona.trahe@intel.com \
--cc=ashish.gupta@marvell.com \
--cc=dev@dpdk.org \
--cc=matan@nvidia.com \
--cc=thomas@monjalon.net \
/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).