From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 5B23C3256 for ; Wed, 21 Jun 2017 15:07:31 +0200 (CEST) Received: from fmsmga003.fm.intel.com ([10.253.24.29]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 21 Jun 2017 06:07:21 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.39,369,1493708400"; d="scan'208";a="870269098" Received: from silpixa00399464.ir.intel.com (HELO silpixa00399464.ger.corp.intel.com) ([10.237.222.157]) by FMSMGA003.fm.intel.com with ESMTP; 21 Jun 2017 06:07:19 -0700 From: Pablo de Lara To: declan.doherty@intel.com, thomas@monjalon.net Cc: dev@dpdk.org, Pablo de Lara Date: Wed, 21 Jun 2017 06:07:29 +0100 Message-Id: <20170621050733.88850-1-pablo.de.lara.guarch@intel.com> X-Mailer: git-send-email 2.9.4 In-Reply-To: <20170620232555.82244-1-pablo.de.lara.guarch@intel.com> References: <20170620232555.82244-1-pablo.de.lara.guarch@intel.com> Subject: [dpdk-dev] [PATCH v2 0/4] Socket ID check removal X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 21 Jun 2017 13:07:31 -0000 Several libraries, drivers and tests check if a socket is within the range of available sockets, by implementig their own function, which returns the total number of sockets that have memory. First of all, this function is not completely correct, as it really returns the highest socket id that has memory. So, if all the sockets up to that one has memory, then it really returns the total number of sockets with memory, but if there is at least one in the middle without memory, then total number of sockets should be less than the value returned. Besides, this function is not really useful, as the main goal is to check if memory on a specific socket is available, rather than checking if a socket id is beyond the total number of sockets. Therefore, it is better to remove the check and let the memory allocation function handle an incorrect socket. Changes in v2: - Removed new EAL function and just removed the socket id check, instead of creating a new function. Pablo de Lara (4): cryptodev: remove socket id check crypto/scheduler: remove socket id check net/bonding: remove socket id check test/bonding: remove socket id check drivers/crypto/scheduler/scheduler_pmd.c | 22 ---------------------- drivers/net/bonding/rte_eth_bond_api.c | 16 ---------------- drivers/net/bonding/rte_eth_bond_args.c | 4 ++-- drivers/net/bonding/rte_eth_bond_pmd.c | 6 ------ drivers/net/bonding/rte_eth_bond_private.h | 3 --- lib/librte_cryptodev/rte_cryptodev.c | 22 ---------------------- test/test/virtual_pmd.c | 17 ----------------- 7 files changed, 2 insertions(+), 88 deletions(-) -- 2.9.4