From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: OpenSSL libcrypto PMD name Date: Mon, 10 Oct 2016 13:36:37 +0200 Message-ID: <2254713.m5JxJRtkTJ@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: pablo.de.lara.guarch@intel.com, declan.doherty@intel.com 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) List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 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.