From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH 2/2] crypto/aesni_mb: add new option to select SIMD mode Date: Fri, 02 Dec 2016 11:37:51 +0100 Message-ID: <2408315.PI9TjJa4bq@xps13> References: <1480671985-3677-1-git-send-email-declan.doherty@intel.com> <1480671985-3677-3-git-send-email-declan.doherty@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: Declan Doherty Return-path: Received: from mail-wm0-f45.google.com (mail-wm0-f45.google.com [74.125.82.45]) by dpdk.org (Postfix) with ESMTP id BB56958C8 for ; Fri, 2 Dec 2016 11:37:53 +0100 (CET) Received: by mail-wm0-f45.google.com with SMTP id f82so11778485wmf.1 for ; Fri, 02 Dec 2016 02:37:53 -0800 (PST) In-Reply-To: <1480671985-3677-3-git-send-email-declan.doherty@intel.com> List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2016-12-02 09:46, Declan Doherty: > Add new initialisation option to the aesni_mb_pmd to allow the user to specify > which set of SIMD functions to load from the AESNI Multi-Buffer Crypto for IPsec > library. Why let user choose? Isn't the most recent the better? This PMD and other software crypto PMDs could (should?) override the CFLAGS like rte_acl do, in order to be able to use recent SIMD functions even if it was globally disabled by the compilation target. See my comment in the rte_memset thread.