From: Tom Zanussi <tom.zanussi@linux.intel.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: herbert@gondor.apana.org.au, davem@davemloft.net,
fenghua.yu@intel.com, vkoul@kernel.org, dave.jiang@intel.com,
tony.luck@intel.com, wajdi.k.feghali@intel.com,
james.guilford@intel.com, kanchana.p.sridhar@intel.com,
vinodh.gopal@intel.com, giovanni.cabiddu@intel.com,
linux-kernel@vger.kernel.org, linux-crypto@vger.kernel.org,
dmaengine@vger.kernel.org
Subject: Re: [PATCH v8 08/14] crypto: iaa - Add IAA Compression Accelerator Documentation
Date: Mon, 21 Aug 2023 13:44:33 -0500 [thread overview]
Message-ID: <2f80afbe7c586e7ee9a554787b5daf4f75e85aad.camel@linux.intel.com> (raw)
In-Reply-To: <20230821172015.GB2227@bug>
Hi Pavel,
On Mon, 2023-08-21 at 19:21 +0200, Pavel Machek wrote:
> Hi!
>
> > Because the IAA Compression Accelerator requires significant user
> > setup in order to be used properly, this adds documentation on the
> > iaa_crypto driver including setup, usage, and examples.
> >
> > Signed-off-by: Tom Zanussi <tom.zanussi@linux.intel.com>
>
>
> > +accel-config
> > +------------
> > +
> > +Unlike typical drivers, the iaa_crypto driver does not enable the
> > +device on driver load. Due to complexity and configurability of
> > the
> > +accelerator devices, it was a design decision to have the user
> > +configure the device and manually enable the desired devices and
> > +workqueues.
>
> Is the driver really so special? Is it widely used besides of zswap?
> Could some kind of
> simple default configuration good enough for zswap be provided?
You're right, currently its main use is for zswap (though the original
submission also supported zram).
This idea of a simple default configuration makes sense and has come up
before. I'll try to come up with a good way to accomplish that in the
next revision.
>
> > +The userspace tool to help doing that is called accel-config.
> > Using
> > +accel-config to configure device or loading a previously saved
> > config
> > +is highly recommended. The device can be controlled via sysfs
> > +directly but comes with the warning that do this ONLY if you know
> > +exactly what you are doing. This document will not cover the
> > sysfs
> > +interface but assumes you will be using accel-config.
>
> Not covering the interface here is okay, but we really should have
> description somewhere,
> and there should be pointer to it here.
OK, yeah, that also makes sense - I'll add something for that too.
>
> > +++ b/Documentation/driver-api/crypto/iaa/index.rst
> > @@ -0,0 +1,20 @@
> > +.. SPDX-License-Identifier: GPL-2.0
> > +
> > +=================================
> > +IAA (Intel Analytics Accelerator)
> > +=================================
> > +
> > +IAA provides hardware compression and decompression via the crypto
> > +API.
>
> Why is it called "analytics accelerator" when its main function is
> compression?
>
Well, the compression/decompression functions are only a part of what
the hardware provides, so I guess the designers used 'analytics
accelerator' as an umbrella term covering everything.
From the hardware documentation, the IAA hardware "provides very high
throughput compression and decompression combined with analytics
primitive functions. The analytic functions are commonly used for
filtering data during analytic query processing. It primarily targets
applications such as big-data and in-memory analytics databases, as
well as application-transparent usages such as memory page
compression."
Hope that helps explain the naming..
Tom
> Best regards,
>
> Pavel
next prev parent reply other threads:[~2023-08-21 19:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 21:29 [PATCH v8 00/14] crypto: Add Intel Analytics Accelerator (IAA) crypto compression driver Tom Zanussi
2023-07-31 21:29 ` [PATCH v8 01/14] dmaengine: idxd: add wq driver name support for accel-config user tool Tom Zanussi
2023-08-02 15:17 ` Fenghua Yu
2023-08-02 16:58 ` Tom Zanussi
2023-08-03 11:36 ` Vinod Koul
2023-07-31 21:29 ` [PATCH v8 02/14] dmaengine: idxd: add external module driver support for dsa_bus_type Tom Zanussi
2023-08-03 13:14 ` Vinod Koul
2023-07-31 21:29 ` [PATCH v8 03/14] dmaengine: idxd: Export drv_enable/disable and related functions Tom Zanussi
2023-08-03 13:15 ` Vinod Koul
2023-08-03 14:24 ` Tom Zanussi
2023-08-03 15:24 ` Dave Jiang
2023-07-31 21:29 ` [PATCH v8 04/14] dmaengine: idxd: Export descriptor management functions Tom Zanussi
2023-08-03 13:16 ` Vinod Koul
2023-07-31 21:29 ` [PATCH v8 05/14] dmaengine: idxd: Export wq resource " Tom Zanussi
2023-08-03 13:17 ` Vinod Koul
2023-07-31 21:29 ` [PATCH v8 06/14] dmaengine: idxd: Add wq private data accessors Tom Zanussi
2023-08-03 13:17 ` Vinod Koul
2023-07-31 21:29 ` [PATCH v8 07/14] dmaengine: idxd: add callback support for iaa crypto Tom Zanussi
2023-08-03 13:19 ` Vinod Koul
2023-07-31 21:29 ` [PATCH v8 08/14] crypto: iaa - Add IAA Compression Accelerator Documentation Tom Zanussi
2023-08-21 17:21 ` Pavel Machek
2023-08-21 18:44 ` Tom Zanussi [this message]
2023-07-31 21:29 ` [PATCH v8 09/14] crypto: iaa - Add Intel IAA Compression Accelerator crypto driver core Tom Zanussi
2023-07-31 21:29 ` [PATCH v8 10/14] crypto: iaa - Add per-cpu workqueue table with rebalancing Tom Zanussi
2023-07-31 21:29 ` [PATCH v8 11/14] crypto: iaa - Add compression mode management along with fixed mode Tom Zanussi
2023-07-31 21:29 ` [PATCH v8 12/14] crypto: iaa - Add support for deflate-iaa compression algorithm Tom Zanussi
2023-07-31 21:29 ` [PATCH v8 13/14] crypto: iaa - Add irq support for the crypto async interface Tom Zanussi
2023-07-31 21:29 ` [PATCH v8 14/14] crypto: iaa - Add IAA Compression Accelerator stats Tom Zanussi
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=2f80afbe7c586e7ee9a554787b5daf4f75e85aad.camel@linux.intel.com \
--to=tom.zanussi@linux.intel.com \
--cc=dave.jiang@intel.com \
--cc=davem@davemloft.net \
--cc=dmaengine@vger.kernel.org \
--cc=fenghua.yu@intel.com \
--cc=giovanni.cabiddu@intel.com \
--cc=herbert@gondor.apana.org.au \
--cc=james.guilford@intel.com \
--cc=kanchana.p.sridhar@intel.com \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=tony.luck@intel.com \
--cc=vinodh.gopal@intel.com \
--cc=vkoul@kernel.org \
--cc=wajdi.k.feghali@intel.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