From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id A7EC3A04B3 for ; Sat, 9 Nov 2019 22:26:51 +0100 (CET) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 093E01BEEE; Sat, 9 Nov 2019 22:26:51 +0100 (CET) Received: from mta-p6.oit.umn.edu (mta-p6.oit.umn.edu [134.84.196.206]) by dpdk.org (Postfix) with ESMTP id 7A7D91BEED for ; Sat, 9 Nov 2019 22:26:50 +0100 (CET) Received: from localhost (unknown [127.0.0.1]) by mta-p6.oit.umn.edu (Postfix) with ESMTP id B1D0F7B3 for ; Sat, 9 Nov 2019 21:26:49 +0000 (UTC) X-Virus-Scanned: amavisd-new at umn.edu Received: from mta-p6.oit.umn.edu ([127.0.0.1]) by localhost (mta-p6.oit.umn.edu [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id q77K2M5RBjxD for ; Sat, 9 Nov 2019 15:26:49 -0600 (CST) Received: from mail-yw1-f72.google.com (mail-yw1-f72.google.com [209.85.161.72]) (using TLSv1.2 with cipher AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mta-p6.oit.umn.edu (Postfix) with ESMTPS id 89AC01D5 for ; Sat, 9 Nov 2019 15:26:49 -0600 (CST) Received: by mail-yw1-f72.google.com with SMTP id t188so8172648ywc.18 for ; Sat, 09 Nov 2019 13:26:49 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=umn.edu; s=google; h=mime-version:from:date:message-id:subject:to; bh=23BMyAFYoygSLWNM8gIvKKeesgZ2fSQxmRlxN4IOfRo=; b=ARVq8bLfsEcvNGFI2VgM9+r6u+7CNu5qADFArXBLm0hOV72n4GAAWbIm/YrgmDsBpD n4cOroLgYfxu5tMMF+/Wx8YxnhwTfmiEfgXRlL3d7AJc7rhmy++qAlhwovPDIgn9tQOs f0FeOjN5IiwhtW5k+a1EjBZMIYZRT1ssXOsZ+AAbW7mv49OW5R/gvg7TK0H5Mlff/UA0 0Tn4x+6rSW+PSGL4d8RlaEZbmMbnV9VzEMPL2nfNQ+Vc5K5BFh0C/SW6JAR/2NrMuoBm a7rNQIsGxpGKjpcXCGGG1s3m1R6M7G9j81eDdmAHlR1Y/8xoz8O0Yr+5YPNtRZFbrhFA iRtg== 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=23BMyAFYoygSLWNM8gIvKKeesgZ2fSQxmRlxN4IOfRo=; b=JXlXmyvVanp/0yfAlTmSKrj10NT9hm12k4KMC5hONNh3KKprlo+1OFfJ3Q18tpPgRC lLtfibcnP6s2oIJh14bDX7Pfde7svR4bPalrr5kQaQ2mGSgOzYZsSVpDLJamBv95XZyN L5Cn0ZMksKdGIdYU3/0ytzVfRqN+FeH8FWmL1eNys1ktDQ4xItsYze5RqjeIC8vlTgUg Zh24/xNvBrg1VVv9dKqFmwe8E1IQEkqIg6C/0Ye242cD54A6iqE9JBeaTLXfPTkt+2JR dIh9zjjqbVhyk9KIed43BY8A4gYF40B/QdILLkMdleaC9tA61TePNBp0cD3tBlZrx6I3 rv7A== X-Gm-Message-State: APjAAAV5usaG0UvxBdpt2F6FwPzn3na/rkaCG5TeOGat/+Ywrpe2e+SD V42vPoLBin13en6JL7ZjzTDddWRK5ecBi7o6y7SsjMcWdc8bZEygLk1VTKACS0UJmoEcuirqbEl +eTAN1RAaI7VkKvNZCBfmBL4uvQ== X-Received: by 2002:a81:3497:: with SMTP id b145mr11745084ywa.315.1573334808600; Sat, 09 Nov 2019 13:26:48 -0800 (PST) X-Google-Smtp-Source: APXvYqx1vFJbRROpQVmp168Zy8zKp1zBLLnef3tQvBOPiTpatnEmv1/hWGqslDm7pI3ZZ9qrK4OiGriQg3GyofzO1kY= X-Received: by 2002:a81:3497:: with SMTP id b145mr11745069ywa.315.1573334808155; Sat, 09 Nov 2019 13:26:48 -0800 (PST) MIME-Version: 1.0 From: Eric Kuha Date: Sat, 9 Nov 2019 15:26:37 -0600 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 Device not initializing 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" Hello, We are working on a DPDK-based project. We are using DPDK 18.11, with Mellanox Connect X-5 EN NICs and mlx5 driver. I set the CONFIG_RTE_LIBRTE_PMD_OPENSSL flag and recompiled DPDK. But, rte_cryptodev_driver_id_get(RTE_STR(CRYPTO_NAME)) with CRYPT_NAME defined as "crypto_openssl", it's returning -1. I cannot seem to initialize any sort of crypto device. Even for testing the library. Any advice for best practices? What might I be missing?