From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id C5ED4A0679 for ; Mon, 29 Apr 2019 09:48:00 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 0AA461B1EE; Mon, 29 Apr 2019 09:48:00 +0200 (CEST) Received: from mail-vs1-f42.google.com (mail-vs1-f42.google.com [209.85.217.42]) by dpdk.org (Postfix) with ESMTP id 822D21B19A for ; Mon, 29 Apr 2019 09:47:58 +0200 (CEST) Received: by mail-vs1-f42.google.com with SMTP id g187so5344590vsc.8 for ; Mon, 29 Apr 2019 00:47:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:from:date:message-id:subject:to; bh=SNRK5TnlywyQ9xRmlkvTTLyjNNVILaD8qY+SgMDJt78=; b=nQIfs/h3eRKthcNo1tyDyq64GtZvyNgsd0ltDMtXtfy68HAQdSZzZQNGkicIrQNMgu MVrQmGFJF+Dh6o47r3lxrTrMdShq9NZJb+d601daiFulOMbnNkLtE484EXa0CeQ+ACj4 p5QtHWHFebZApOK/sTZJkd0oH++bvKau0lsExxlwfqHrnENo0XR34dODkGCajJ0/1+K5 HsZI1UeOA5a/agWf8dssMp3Q8TrX1gpEBNsl+6QIp3EVgPD1J3eAZwhUwBDWCGp1i8Yb ZMr/ZVy40iaD9/k/Pk8G8EH+z4sKj8EW83YPij1zQ1TGw1kjavGGNkOpjIZ2vx4MIwA/ 5TyQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=SNRK5TnlywyQ9xRmlkvTTLyjNNVILaD8qY+SgMDJt78=; b=YhvzkhUtIXXV4VSzut2LUZEZP5kLS1SGVTN0mTtzE5s4lU6+lfyeIThPvLgrOaiTXy lyLqfpim21+2z6lrGGBiWwSjel8uZ4a1zsgI3BgvQROG1Ldia5ePOiUk9YzrzQXSBWnM 9tM8igBZbQr6nUtjgquz71j0tmjiQJ6rwnAQ/5UNYeq2qiwMGXdgEkNLClmzuNo7Ju7q 4OwyWwdMfSbe+oiTUmkmbd0wWlSm9IL1p8UBYOiVRzQKLdMuujg+azbmwMTb3oLnO2NX vXwA6c7yywgcPATfqMxiBmZqBjQMIncuF+v/qFdobYwAgb6rcSIBv28W7dZyRbMm4qU+ ZQ0Q== X-Gm-Message-State: APjAAAVXQsnPXoyeOZL+fiyaf1YiUOsqGJ2LPYNx3B+OPf/etcz9ivBE ZqJhkVf2TFTctMr+u9xFQF0fv/OVgzd9B5gpTuwFIGje X-Google-Smtp-Source: APXvYqxdhhDK+zNHWorljeKMi7TT4QnZGMoBl7YLq4qEMK/A81kKLPA5EqTn1H36DKfIqqd7nZXnIN9/EjQlyq6499A= X-Received: by 2002:a67:b707:: with SMTP id h7mr9498854vsf.213.1556524077537; Mon, 29 Apr 2019 00:47:57 -0700 (PDT) MIME-Version: 1.0 From: Jitendra Saini Date: Mon, 29 Apr 2019 13:17:21 +0530 Message-ID: To: users@dpdk.org Content-Type: text/plain; charset="UTF-8" X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: [dpdk-users] Crypto-dev schedular - Support for multiple crypto algorithms concurrently X-BeenThere: users@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK usage discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: users-bounces@dpdk.org Sender: "users" Hi All, *Context*: Using dpdk + vpp for telecom network user plane 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?* 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*) *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: *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* Best Regads, Jitendra