From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lf0-f49.google.com (mail-lf0-f49.google.com [209.85.215.49]) by dpdk.org (Postfix) with ESMTP id C0C826943 for ; Mon, 10 Oct 2016 13:36:39 +0200 (CEST) Received: by mail-lf0-f49.google.com with SMTP id x79so122314155lff.0 for ; Mon, 10 Oct 2016 04:36:39 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:user-agent:mime-version :content-transfer-encoding; bh=mzuUkHelO3oH582/s3mN2k9rOJOpdY0l9aogVa3hQbc=; b=ZLm79H/8mNT89tpT9xjlbFk0p/BIUU45OMdCVzMzrhFZlRLmh3YF8yJ83U1a3uF52R 5z3Eu4jBmcmzoCBHLbt1Bzv6A4pCgD2K0FV0mBcddQkjT41KIJaUQ4+Sob/zEeUyqJqQ sAIaif1GRv023K3Oincs5AX8SGFstH9r2g7A0aFT/WaajcsZk+u31D8IbkafWvDltf0a BHbjPr4y5h2l/z/sp8Z/I3hb86BbocmGmWv2RRwv6WUDQE4GPCcSIUPiKXfnB+tPgKgG Y5T7ihnfG6j3zxXHAZ0+OdzDIvwyySBIJ37ymgFjy6zi+/QukBD//D7+FvY6Uxhog80/ vBCQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:user-agent :mime-version:content-transfer-encoding; bh=mzuUkHelO3oH582/s3mN2k9rOJOpdY0l9aogVa3hQbc=; b=Y1g+dhHe7l9DoGzdbg9Z4axUPgwUKEmItHWdeZvXNnH88fFiAPcwCAhgH1KW6usfni fMZk56I5+hvRpJXM1Ia8wcvz2RGDdhcGzDgybZEeOx7SohVp7X6x42gdhN+tlDRAGbiF idxDsJ7HB/UhvpzxBWDEX7j9hIv2OGWJjJpdTXTuJH5cC+BYXA61bbfLZgv5IWWAS+Wk a8Cv2O5k7wBR24+SPYlSrLWgKDgva8M8lhF0cUTymhaFP+HsY9a95tf/sFu4WfAaBSZO BTEdibMvGW0OTxVmmCdY0YqZK3Ds6tfiCED+ZLpuWLdwunN++Rtkonm9upGB9jZPZWP0 2d2w== X-Gm-Message-State: AA6/9RmSLE0VhoXj9wxWVQGQ600xYtHgYLBv0EJKaLsHDM0BfWsFr9lidIbC+QzgzQme9hWU X-Received: by 10.25.31.82 with SMTP id f79mr15430746lff.38.1476099399209; Mon, 10 Oct 2016 04:36:39 -0700 (PDT) Received: from xps13.localnet (184.203.134.77.rev.sfr.net. [77.134.203.184]) by smtp.gmail.com with ESMTPSA id o10sm6046143lfo.47.2016.10.10.04.36.38 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 10 Oct 2016 04:36:38 -0700 (PDT) From: Thomas Monjalon To: pablo.de.lara.guarch@intel.com, declan.doherty@intel.com Cc: dev@dpdk.org Date: Mon, 10 Oct 2016 13:36:37 +0200 Message-ID: <2254713.m5JxJRtkTJ@xps13> User-Agent: KMail/4.14.10 (Linux/4.5.4-1-ARCH; KDE/4.14.11; x86_64; ; ) MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: [dpdk-dev] OpenSSL libcrypto PMD name X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2016 11:36:40 -0000 Hi, I would like to raise a naming issue in crypto. In the crypto side of DPDK, we have a library (similar to ethdev) for crypto API and device interface: http://dpdk.org/browse/dpdk/tree/lib/librte_cryptodev There are also some drivers (which are some libraries): http://dpdk.org/browse/dpdk/tree/drivers/crypto Most of them (6/8) are some DPDK wrappers for external libraries. Recently was introduced the libcrypto PMD which is a wrapper for the OpenSSL libcrypto. As we already have a lot of crypto libraries, I'm afraid the name libcrypto is really confusing. Why not call it openssl PMD? PS: I know OpenSSL has 2 libraries - ssl and crypto - but I do not expect any high-level SSL feature in a crypto driver. So drivers/crypto/openssl should not be confusing.