Hi Phil,
Thanks for your reply.
Yes. The QAT 1.5 module is loaded. I verified that by:
cat /proc/icp_c2xxx_dev0/version
+--------------------------------------------------+
| Hardware and Software versions for device 0
|
+--------------------------------------------------+
Hardware Version: B0 SKU1
Firmware Version:
1.3.0
MMP Version:
1.0.0
Driver Version:
1.3.0
+--------------------------------------------------+
lsmod also shows the o/p, that the driver is loaded.
lsmod | grep icp
The following is displayed:
# icp_qat_netkey 6748 0
# icp_qa_al 1334748 2 icp_qat_netkey
Also, when I started IPSec traffic, the counters were increasing.
How can I confirm that the upstream has support for C2xxx?
It would be great if you can point me to the piece of code in upstream
which has support for any other acceleration. I can maybe research from
there on how can I add support for C2xxx?
Thank you,
--
Chirag
On Thu, Feb 2, 2017 at 5:47 AM, Phil Sutter <p...@nwl.cc> wrote:
> Hi Chirag,
>
> On Tue, Jan 31, 2017 at 10:58:15AM -0800, Chirag Shahani wrote:
> [...]
> > However, when I running the same user space program on a box which has
> SoC
> > C2000 co-processor (QAT-1.5), I was expecting the code to* NOT *print
> > printf("Note: This is not an accelerated cipher\n").
> >
> >
> >
> > * if (!(siop.flags & SIOP_FLAG_KERNEL_DRIVER_ONLY)) {
> > printf("Note: This is not an accelerated cipher\n"); }*
> >
> > Could anyone please let me know what I am missing and what is required to
> > make sure the accelerated cipher is used iso of the linux kernel to do
> the
> > encrypt/ decrypt functions.
>
> Looks like you're missing a kernel driver for the crypto engine. Is any
> of the qat_* modules loaded? Do you see any accelerated ciphers in
> /proc/crypto? I didn't have a closer look, but it looks like upstream
> doesn't support the C2xxx series at all.
>
> Cheers, Phil
>
_______________________________________________
Cryptodev-linux-devel mailing list
Cryptodev-linux-devel@gna.org
https://mail.gna.org/listinfo/cryptodev-linux-devel
