Hi Sergio, Jitendra
Note that there is a bug in VPP device initialization where the scheduler needs
to appear before the slaves in the config (easy to workaround it).
could you help tell me how to resolve this issue, I also found the crypto
scheduler doesn't work, thanks!
Best Rregards
Dave
________________________________
发件人: vpp-dev@lists.fd.io <vpp-dev@lists.fd.io> 代表 Sergio G.M.
<sgmon...@gmail.com>
发送时间: 2019年5月6日 21:19
收件人: dmar...@me.com <dmar...@me.com>
抄送: Jitendra Saini <sainijite...@gmail.com>; vpp-dev@lists.fd.io
<vpp-dev@lists.fd.io>
主题: Re: [vpp-dev] vpp dpdk crypto dev - are multiple crypto algorithms
supported concurrently? #vpp
Hi Jitendra,
I have not followed DPDK Cryptodev development over the last year, but given my
vague memory and latest VPP code, I reckon your configuration is not supported.
The cryptodev scheduler supports common cipher/auth algorithms among all
slaves, which in your case is none.
Which VPP version are you using? I cannot reproduce with HEAD master branch
(output below),
crypto_scheduler crypto_scheduler down
numa_node 0, max_queues 8
Cipher:
Auth:
enqueue 0 dequeue 0 enqueue_err 0 dequeue_err 0
free_resources 0 :
used_resources 0 :
aesni_gcm0 crypto_aesni_gcm up
numa_node 0, max_queues 2
SYMMETRIC_CRYPTO, SYM_OPERATION_CHAINING, CPU_AVX2, CPU_AESNI,
OOP_SGL_IN_LB_OUT, OOP_LB_IN_LB_OUT
Cipher: aes-gcm-128, aes-gcm-192, aes-gcm-256
Auth:
enqueue 0 dequeue 0 enqueue_err 0 dequeue_err 0
free_resources 1 :
thr_id -1 qp 1 inflight 0
used_resources 1 :
thr_id 0 qp 0 inflight 0
aesni_mb0 crypto_aesni_mb up
numa_node 0, max_queues 2
SYMMETRIC_CRYPTO, SYM_OPERATION_CHAINING, CPU_AVX2, CPU_AESNI
Cipher: aes-cbc-128, aes-cbc-192, aes-cbc-256, aes-ctr-128, aes-ctr-192,
aes-ctr-256, aes-gcm-128, aes-gcm-192, aes-gcm-256
Auth: md5-96, sha1-96, sha-256-96, sha-256-128, sha-384-192, sha-512-256
enqueue 0 dequeue 0 enqueue_err 0 dequeue_err 0
free_resources 1 :
thr_id -1 qp 1 inflight 0
used_resources 1 :
thr_id 0 qp 0 inflight 0
Note that there is a bug in VPP device initialization where the scheduler needs
to appear before the slaves in the config (easy to workaround it).
My guess is that the issue you are seeing got fixed (not valid) at some point
by DPDK.
HTH,
Sergio
On Fri, May 3, 2019 at 11:05 AM Damjan Marion via
Lists.Fd.Io<http://Lists.Fd.Io>
<dmarion=me....@lists.fd.io<mailto:me....@lists.fd.io>> wrote:
Majority of people who work on VPP actively (including me) are not very
familiar about dpdk cryptodev which
probably explains why you are not getting any response.
Please note that there is currently undergoing big rework of ipsec / crypto
where goals are improvement of
native crypto, deprecating ipsec code inside dpdk plugin and implementation of
native crypto scheduler.
―
Damjan
> On 2 May 2019, at 14:04, Jitendra Saini
> <sainijite...@gmail.com<mailto:sainijite...@gmail.com>> wrote:
>
> Hello,
>
> Sorry for repost.. I had posted this query 2 days ago but did not get any
> update. Help from your side will be much useful.
>
> Context: Using dpdk + vpp for user plane packet processing
> Desired: want to use dpdk crypto-dev scheduler to have 2 cores dedicated for
> crypto operations
> Issue: crypto devices of different types (AES_MB & AES_GCM) are not supported
> concurrently.
> Query: Have anyone used crypto scheduler and able to support multiple crypto
> device types? Any way to have such support enabled?
>
> Details:
> We want to use 4 cores in total for user plane processing with following
> deployment
> Core-1: vpp worker thread - downlink
> Core-2 : vpp worker thread - uplink
> Core-3 : crypto-slave-1 (Cipher: aes-cbc-128)
> Core-4 : crypto-slave-2 (Cipher: aes-gcm-128)
>
> Configurations:
> vdev crypto_aesni_mb_pmd1,name=aesni_mb_1,socket_id=0
> vdev crypto_aesni_gcm_pmd1,name=aesni_gcm_1,socket_id=0
> vdev
> crypto_scheduler,slave=aesni_mb_1,slave=aesni_gcm_1,mode=multi-core,corelist=3-4,ordering=enable,slave_buff_size=8192
>
> Query - Detail : with above log output, we see crypto-slaves aesni_mb_1 &
> aesni_gcm_1 deployed on both worker threads but from Test Results we see
> following -
> AES Traffic - works through crypto scehdular
> GCM Traffic - does not work. (Error - dpdk-esp-decrypt Failed to
> get crypto session)
>
> Can someone please help to understand this behavior / suggest if any approach
> worked for you to support multiple crypto algorithms?
> Thanks in advance
>
> Log output below -
> vpp# sh dpdk crypto devices
> aesni_mb_1 crypto_aesni_mb up
> numa_node 0, max_queues 8
> free_resources 2, used_resources 2
> SYMMETRIC_CRYPTO, SYM_OPERATION_CHAINING, CPU_AVX2, CPU_AESNI
> Cipher: aes-cbc-128, aes-cbc-192, aes-cbc-256, aes-ctr-128, aes-ctr-192,
> aes-ctr-256
> Auth: md5-96, sha1-96, sha-256-128, sha-384-192, sha-512-256,
> aes-xcbc-mac-96
>
> aesni_gcm_1 crypto_aesni_gcm up
> numa_node 0, max_queues 8
> free_resources 2, used_resources 2
> SYMMETRIC_CRYPTO, SYM_OPERATION_CHAINING, CPU_AVX2, CPU_AESNI,
> MBUF_SCATTER_GATHER
> Cipher: aes-gcm-128, aes-gcm-192, aes-gcm-256
> Auth: aes-gmac-128, aes-gmac-256
>
> crypto_scheduler crypto_scheduler up
> numa_node 0, max_queues 8
> free_resources 2, used_resources 2
> SYMMETRIC_CRYPTO, SYM_OPERATION_CHAINING, CPU_AVX2, CPU_AESNI,
> MBUF_SCATTER_GATHER
> Cipher: aes-gcm-128, aes-gcm-192, aes-gcm-256
> Auth:
>
>
> vpp# sh dpdk crypto placement verbose
> Thread 1 (vpp_wk_0):
> aesni_mb_1 dev-id 0 inbound-queue 0 outbound-queue 1
> Cipher: aes-cbc-128, aes-cbc-192, aes-cbc-256, aes-ctr-128, aes-ctr-192,
> aes-ctr-256
> Auth: md5-96, sha1-96, sha-256-128, sha-384-192, sha-512-256,
> aes-xcbc-mac-96
> aesni_gcm_1 dev-id 1 inbound-queue 0 outbound-queue 1
> Cipher:
> Auth: aes-gmac-128, aes-gmac-256
> crypto_scheduler dev-id 2 inbound-queue 0 outbound-queue 1
> Cipher: aes-gcm-128, aes-gcm-192, aes-gcm-256
> Auth:
>
> Thread 2 (vpp_wk_1):
> aesni_mb_1 dev-id 0 inbound-queue 2 outbound-queue 3
> Cipher: aes-cbc-128, aes-cbc-192, aes-cbc-256, aes-ctr-128, aes-ctr-192,
> aes-ctr-256
> Auth: md5-96, sha1-96, sha-256-128, sha-384-192, sha-512-256,
> aes-xcbc-mac-96
> aesni_gcm_1 dev-id 1 inbound-queue 2 outbound-queue 3
> Cipher:
> Auth: aes-gmac-128, aes-gmac-256
> crypto_scheduler dev-id 2 inbound-queue 2 outbound-queue 3
> Cipher: aes-gcm-128, aes-gcm-192, aes-gcm-256
> Auth:
>
> Thanks
> Best Regards,
> Jitendra Saini
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
>
> View/Reply Online (#12896): https://lists.fd.io/g/vpp-dev/message/12896
> Mute This Topic: https://lists.fd.io/mt/31453891/675642
> Mute #vpp: https://lists.fd.io/mk?hashtag=vpp&subid=1480514
> Group Owner: vpp-dev+ow...@lists.fd.io<mailto:vpp-dev%2bow...@lists.fd.io>
> Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
> [dmar...@me.com<mailto:dmar...@me.com>]
> -=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#12917): https://lists.fd.io/g/vpp-dev/message/12917
Mute This Topic: https://lists.fd.io/mt/31453891/682142
Mute #vpp: https://lists.fd.io/mk?hashtag=vpp&subid=1498673
Group Owner: vpp-dev+ow...@lists.fd.io<mailto:vpp-dev%2bow...@lists.fd.io>
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub
[sergio.gonzalez.mon...@outlook.com<mailto:sergio.gonzalez.mon...@outlook.com>]
-=-=-=-=-=-=-=-=-=-=-=-
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#13926): https://lists.fd.io/g/vpp-dev/message/13926
Mute This Topic: https://lists.fd.io/mt/31453891/21656
Mute #vpp: https://lists.fd.io/mk?hashtag=vpp&subid=1480452
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-
