De : <vpp-dev@lists.fd.io> au nom de "amitmulay...@gmail.com" 
<amitmulay...@gmail.com>
Date : lundi 5 août 2019 à 07:21
À : "vpp-dev@lists.fd.io" <vpp-dev@lists.fd.io>
Objet : [vpp-dev] ipsec traffic backend

Hello Guys
i wanted to ask how can i know if my ipsec is running with QAT (intel quick 
assist) traffic backend (i am sure that i have a cpu that supports it..)?

You need a QAT PCI card….

i'm sure that it is not OPEN SLL becouse i see dpdk on those outputs


 DBGvpp# show ipsec backends
IPsec ESP backends available:
           Name                     Index             Active
 default openssl backend              0                 no
       dpdk backend                        1                 yes
DBGvpp# show dpdk crypto devices
crypto_aesni_mb0         crypto_aesni_mb     up
  numa_node 0, max_queues 8
  free_resources 3, used_resources 1
  SYMMETRIC_CRYPTO, SYM_OPERATION_CHAINING, CPU_SSE, 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-128, sha-384-192, sha-512-25

DBGvpp# show dpdk crypto placement
Thread 0 (vpp_main):
  crypto_aesni_mb0     dev-id  0 inbound-queue  0 outbound-queue  1


DBGvpp# show log
2019/ 8/ 1 06:24:20:647 warn       dpdk       EAL init args: -c 2 -n 4 
--in-memory --vdev crypto_aesni_mb0 --file-prefix vpp --master-lcore 1
2019/ 8/ 1 06:24:23:365 notice     dpdk       DPDK drivers found 6 ports...
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL: Some devices want iova as va 
but pa will be used because.. EAL: vfio-noiommu mode configured
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL: No free hugepages reported 
in hugepages-1048576kB
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL: No free hugepages reported 
in hugepages-1048576kB
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL: No free hugepages reported 
in hugepages-1048576kB
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL: VFIO support initialized
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL: WARNING! Base virtual 
address hint (0x1400001000 != 0x1440000000) not respected!
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL:    This may cause issues 
with mapping memory into secondary processes
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL: WARNING! Base virtual 
address hint (0x1c40002000 != 0x1c80000000) not respected!
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL:    This may cause issues 
with mapping memory into secondary processes
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL: WARNING! Base virtual 
address hint (0x2480003000 != 0x24c0000000) not respected!
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL:    This may cause issues 
with mapping memory into secondary processes
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL: WARNING! Base virtual 
address hint (0x2cc0064000 != 0x2cc0200000) not respected!
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL:    This may cause issues 
with mapping memory into secondary processes
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL: WARNING! Base virtual 
address hint (0x30c02c5000 != 0x30c0400000) not respected!
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL:    This may cause issues 
with mapping memory into secondary processes
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL: WARNING! Base virtual 
address hint (0x34c0526000 != 0x34c0600000) not respected!
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL:    This may cause issues 
with mapping memory into secondary processes
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL: WARNING! Base virtual 
address hint (0x38c0787000 != 0x38c0800000) not respected!
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL:    This may cause issues 
with mapping memory into secondary processes
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL:   Invalid NUMA socket, 
default to 0
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL:   using IOMMU type 1 (Type 1)
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL:   Invalid NUMA socket, 
default to 0
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL:   Invalid NUMA socket, 
default to 0
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL:   Invalid NUMA socket, 
default to 0
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL:   Invalid NUMA socket, 
default to 0
2019/ 8/ 1 06:24:23:378 notice     dpdk       EAL:   Invalid NUMA socket, 
default to 0
2019/ 8/ 1 06:24:23:378 notice     dpdk       Invalid port_id=6

cat /etc/vpp/startup.conf:
        dpdk {
                vdev crypto_aesni_mb0

… whose PCI address you specify here.

                #vdev crypto_aesni_gcm_mb1
                dev default {
                         num-rx-desc 512
                         num-tx-desc 512
                }
        num-mbufs 20000
        socket-mem 1024
        }

DBGvpp# show version
vpp v19.01.2-release
does this all mean that im using QAT? or "regular" dpdk ?
this config uses a SW/virtual device
/neale


if not how can i make sure im using it?
thanks all !!

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.

View/Reply Online (#13669): https://lists.fd.io/g/vpp-dev/message/13669
Mute This Topic: https://lists.fd.io/mt/32722882/21656
Group Owner: vpp-dev+ow...@lists.fd.io
Unsubscribe: https://lists.fd.io/g/vpp-dev/unsub  [arch...@mail-archive.com]
-=-=-=-=-=-=-=-=-=-=-=-

Reply via email to