From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v2] eal: add function to return number of detected sockets Date: Tue, 16 Jan 2018 13:20:12 +0100 Message-ID: <2134391.uA7JBUhxlf@xps> References: <3f9df1ca17e97b2df560d5af5fa31a778af3263f.1513942728.git.anatoly.burakov@intel.com> <7548056.EcYGU9teXu@xps> <6a6fd300-2523-f50a-3be4-461724a70fe0@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: "Burakov, Anatoly" Return-path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id 4966212001 for ; Tue, 16 Jan 2018 13:20:45 +0100 (CET) In-Reply-To: <6a6fd300-2523-f50a-3be4-461724a70fe0@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" 16/01/2018 12:56, Burakov, Anatoly: > On 12-Jan-18 11:50 AM, Thomas Monjalon wrote: > > 12/01/2018 12:44, Burakov, Anatoly: > >> On 11-Jan-18 10:20 PM, Thomas Monjalon wrote: > >>> 22/12/2017 13:41, Anatoly Burakov: > >>>> During lcore scan, find maximum socket ID and store it. > >>>> > >>>> Signed-off-by: Anatoly Burakov > >>>> --- > >>>> --- a/lib/librte_eal/common/include/rte_eal.h > >>>> +++ b/lib/librte_eal/common/include/rte_eal.h > >>>> @@ -83,6 +83,7 @@ enum rte_proc_type_t { > >>>> struct rte_config { > >>>> uint32_t master_lcore; /**< Id of the master lcore */ > >>>> uint32_t lcore_count; /**< Number of available logical cores. */ > >>>> + uint32_t numa_node_count; /**< Number of detected NUMA nodes. */ > >>>> uint32_t service_lcore_count;/**< Number of available service cores. */ > >>>> enum rte_lcore_role_t lcore_role[RTE_MAX_LCORE]; /**< State of cores. */ > >>> > >>> isn't it breaking the ABI? > >>> > >>> > >> > >> Yep, you're right, forgot to add that. I didn't expect this to get > >> merged in 18.02 anyway, so v2 will follow. > > > > Please write 18.05 in the subject to show your expectation. > > Thanks > > > > Does it have to be an ABI change though? We can put numa_node_count > after pointer to mem_config, in which case it won't be an ABI break. > Would that be better? Changing the size of a struct which is allocated by the app, is an ABI break. Is your solution changing the size?