All of lore.kernel.org
 help / color / mirror / Atom feed
From: Vlad Dronov <vdronov@redhat.com>
To: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
	linux-crypto@vger.kernel.org, qat-linux@intel.com
Subject: Re: [PATCH v2 0/4] crypto: qat - enable configuration for 4xxx
Date: Tue, 28 Jun 2022 14:15:26 +0200	[thread overview]
Message-ID: <CAMusb+SU1AtWf+RQH6r9kxDwKfR0qTrGaB1BfSk0s7gTKjbp_Q@mail.gmail.com> (raw)
In-Reply-To: <20220627083652.880303-1-giovanni.cabiddu@intel.com>

Hi,

On Mon, Jun 27, 2022 at 10:37 AM Giovanni Cabiddu
<giovanni.cabiddu@intel.com> wrote:
>
> qat_4xxx devices can be configured to allow either crypto or compression
> operations. By default, devices are configured statically according
> to following rule:
> - odd numbered devices assigned to compression services
> - even numbered devices assigned to crypto services
>
> This set exposes two attributes in sysfs that allow to report and change
> the state and the configuration of a QAT 4xxx device.
> The first, /sys/bus/pci/devices/<BDF>/qat/state, allows to bring a
> device down in order to change the configuration, and bring it up again.
> The second, /sys/bus/pci/devices/<BDF>/qat/cfg_services, allows to
> inspect the current configuration of a device (i.e. crypto or
> compression) and change it.
>
>     # cat /sys/bus/pci/devices/<BDF>/qat/state
>     up
>     # cat /sys/bus/pci/devices/<BDF>/qat/cfg_services
>     sym;asym
>     # echo down > /sys/bus/pci/devices/<BDF>/qat/state
>     # echo dc > /sys/bus/pci/devices/<BDF>/qat/cfg_services
>     # echo up > /sys/bus/pci/devices/<BDF>/qat/state
>     # cat /sys/bus/pci/devices/<BDF>/qat/state
>     dc
>
> Changes from v1:
>  - Updated target kernel version in documentation (from 5.19 to 5.20).
>  - Fixed commit message in patch #1 and updated documentation in patch
>    #4 after review from Vladis Dronov.
>
> Giovanni Cabiddu (4):
>   crypto: qat - expose device state through sysfs for 4xxx
>   crypto: qat - change behaviour of adf_cfg_add_key_value_param()
>   crypto: qat - relocate and rename adf_sriov_prepare_restart()
>   crypto: qat - expose device config through sysfs for 4xxx

The patchset looks good to me. Please feel free to use:

Reviewed-by: Vladis Dronov <vdronov@redhat.com>

Best regards,
Vladis Dronov | Red Hat, Inc. | The Core Kernel | Senior Software Engineer


  parent reply	other threads:[~2022-06-28 12:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27  8:36 [PATCH v2 0/4] crypto: qat - enable configuration for 4xxx Giovanni Cabiddu
2022-06-27  8:36 ` [PATCH v2 1/4] crypto: qat - expose device state through sysfs " Giovanni Cabiddu
2022-06-27  8:36 ` [PATCH v2 2/4] crypto: qat - change behaviour of adf_cfg_add_key_value_param() Giovanni Cabiddu
2022-06-27  8:36 ` [PATCH v2 3/4] crypto: qat - relocate and rename adf_sriov_prepare_restart() Giovanni Cabiddu
2022-06-27  8:36 ` [PATCH v2 4/4] crypto: qat - expose device config through sysfs for 4xxx Giovanni Cabiddu
2022-06-28 12:15 ` Vlad Dronov [this message]
2022-07-08  7:58 ` [PATCH v2 0/4] crypto: qat - enable configuration " Herbert Xu

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=CAMusb+SU1AtWf+RQH6r9kxDwKfR0qTrGaB1BfSk0s7gTKjbp_Q@mail.gmail.com \
    --to=vdronov@redhat.com \
    --cc=giovanni.cabiddu@intel.com \
    --cc=herbert@gondor.apana.org.au \
    --cc=linux-crypto@vger.kernel.org \
    --cc=qat-linux@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.