From: Giovanni Cabiddu <giovanni.cabiddu@intel.com>
To: Yoan Picchi <yoan.picchi@arm.com>
Cc: Herbert Xu <herbert@gondor.apana.org.au>,
"David S . Miller" <davem@davemloft.net>,
qat-linux@intel.com, linux-crypto@vger.kernel.org,
linux-kernel@vger.kernel.org,
Andre Przywara <andre.przywara@arm.com>,
Ard Biesheuvel <ardb@kernel.org>
Subject: Re: [PATCH 0/2] Crypto: Remove x86 dependency on QAT drivers
Date: Fri, 17 Jun 2022 09:49:20 +0100 [thread overview]
Message-ID: <YqxAEID8lu497CCe@silpixa00400314> (raw)
In-Reply-To: <20220613142535.222041-1-yoan.picchi@arm.com>
Hi Yoan,
On Mon, Jun 13, 2022 at 02:25:33PM +0000, Yoan Picchi wrote:
> The QAT acceleration card can be very helpfull for some tasks like dealing
> with IPSEC but it is currently restricted to be used only on x86 machine.
> Looking at the code we didn't see any reasons why those drivers might not
> work on other architectures. We've successfully built all of them on x86,
> arm64, arm32, mips64, powerpc64, riscv64 and sparc64.
>
> We also have tested the driver with an Intel Corporation C62x Chipset
> QuickAssist Technology (rev 04) PCIe card on an arm64 server. After the numa
> patch, it works with the AF_ALG crypto userland interface, allowing us to
> encrypt some data with cbc for instance. We've also successfully created some
> VF, bound them to DPDK, and used the card this way, thus showing some real
> life usecases of x86 do work on arm64 too.
>
> Changelog v1 ... v2:
> - add COMPILE_TEST to Kconfig
>
> Andre Przywara (1):
> crypto: qat: replace get_current_node() with numa_node_id()
>
> Yoan Picchi (1):
> Removes the x86 dependency on the QAT drivers
Would you mind re-sending the set changing the headline of the commit
messages as reported in the previous email?
https://www.spinics.net/lists/linux-crypto/msg64584.html
Thanks,
--
Giovanni
next prev parent reply other threads:[~2022-06-17 8:49 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-13 14:25 [PATCH 0/2] Crypto: Remove x86 dependency on QAT drivers Yoan Picchi
2022-06-13 14:25 ` [PATCH 1/2] crypto: qat: replace get_current_node() with numa_node_id() Yoan Picchi
2022-06-13 14:25 ` [PATCH 2/2] Removes the x86 dependency on the QAT drivers Yoan Picchi
2022-06-17 8:49 ` Giovanni Cabiddu [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-06-17 9:55 [PATCH 0/2] Crypto: Remove x86 dependency on " Yoan Picchi
2022-06-17 10:10 ` Yoan Picchi
2022-06-07 16:58 Yoan Picchi
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=YqxAEID8lu497CCe@silpixa00400314 \
--to=giovanni.cabiddu@intel.com \
--cc=andre.przywara@arm.com \
--cc=ardb@kernel.org \
--cc=davem@davemloft.net \
--cc=herbert@gondor.apana.org.au \
--cc=linux-crypto@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=qat-linux@intel.com \
--cc=yoan.picchi@arm.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