From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v3 0/3] fix RTE_PROC_PRIMARY_OR_ERR_RET RTE_PROC_PRIMARY_OR_RET Date: Wed, 24 Feb 2016 19:25:31 +0100 Message-ID: <4332341.KWFTSukzC1@xps13> References: <1450873172-21932-1-git-send-email-reshma.pattan@intel.com> <1452011698-27354-1-git-send-email-reshma.pattan@intel.com> <2601191342CEEE43887BDE71AB97725836AE1AF8@irsmsx105.ger.corp.intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: "Pattan, Reshma" Return-path: Received: from mail-wm0-f54.google.com (mail-wm0-f54.google.com [74.125.82.54]) by dpdk.org (Postfix) with ESMTP id 8BB702BE9 for ; Wed, 24 Feb 2016 19:27:06 +0100 (CET) Received: by mail-wm0-f54.google.com with SMTP id c200so283453345wme.0 for ; Wed, 24 Feb 2016 10:27:06 -0800 (PST) In-Reply-To: <2601191342CEEE43887BDE71AB97725836AE1AF8@irsmsx105.ger.corp.intel.com> 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" > > From: reshmapa > > > > Patches 1 and 2 removes RTE_PROC_PRIMARY_OR_ERR_RET and > > RTE_PROC_PRIMARY_OR_RET macro usage from rte_ether and rte_cryptodev libraries to allow API > > access to secondary process. > > > > Patch 3 allows users to configure ethdev with zero rx/tx queues, but both should not be zero. > > Fix rte_eth_dev_tx_queue_config, rte_eth_dev_rx_queue_config to allocate memory for rx/tx queues > > only when number of rx/tx queues are nonzero. > > > > v3: > > * Removed checkpatch fixes of lib/librte_ether/rte_ethdev.h from patch number 1. > > > > Reshma Pattan (3): > > librte_ether: remove RTE_PROC_PRIMARY_OR_ERR_RET and > > RTE_PROC_PRIMARY_OR_RET > > librte_cryptodev: remove RTE_PROC_PRIMARY_OR_RET > > librte_ether: fix rte_eth_dev_configure > > Acked-by: Konstantin Ananyev Applied with these titles: - ethdev: allow full control from secondary process - cryptodev: allow full control from secondary process - ethdev: support unidirectional configuration Please see how it is more informative without using the macros or function names. The title must reflect the intent, not the details. Thanks