From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Burakov, Anatoly" Subject: Re: [PATCH 08/41] eal: make malloc free return resulting malloc element Date: Tue, 20 Mar 2018 09:40:53 +0000 Message-ID: <6f08a72d-c973-70a0-35ad-86b536563a8e@intel.com> References: <757ab0a9ebe0e921c2ab77562cb0333da8334c50.1520083504.git.anatoly.burakov@intel.com> <20180319173457.cbxyj2pummor2g5i@platinum> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: dev@dpdk.org, keith.wiles@intel.com, jianfeng.tan@intel.com, andras.kovacs@ericsson.com, laszlo.vadkeri@ericsson.com, benjamin.walker@intel.com, bruce.richardson@intel.com, thomas@monjalon.net, konstantin.ananyev@intel.com, kuralamudhan.ramakrishnan@intel.com, louise.m.daly@intel.com, nelio.laranjeiro@6wind.com, yskoh@mellanox.com, pepperjo@japf.ch, jerin.jacob@caviumnetworks.com, hemant.agrawal@nxp.com To: Olivier Matz Return-path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id B51974C71 for ; Tue, 20 Mar 2018 10:40:58 +0100 (CET) In-Reply-To: <20180319173457.cbxyj2pummor2g5i@platinum> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 19-Mar-18 5:34 PM, Olivier Matz wrote: > On Sat, Mar 03, 2018 at 01:45:56PM +0000, Anatoly Burakov wrote: >> Signed-off-by: Anatoly Burakov >> --- >> lib/librte_eal/common/malloc_elem.c | 4 ++-- >> lib/librte_eal/common/malloc_elem.h | 2 +- >> lib/librte_eal/common/malloc_heap.c | 4 ++-- >> 3 files changed, 5 insertions(+), 5 deletions(-) >> >> diff --git a/lib/librte_eal/common/malloc_elem.c b/lib/librte_eal/common/malloc_elem.c >> index 008f5a3..c18f050 100644 >> --- a/lib/librte_eal/common/malloc_elem.c >> +++ b/lib/librte_eal/common/malloc_elem.c >> @@ -379,7 +379,7 @@ malloc_elem_join_adjacent_free(struct malloc_elem *elem) >> * blocks either immediately before or immediately after newly freed block >> * are also free, the blocks are merged together. >> */ >> -int >> +struct malloc_elem * >> malloc_elem_free(struct malloc_elem *elem) >> { >> void *ptr; >> @@ -397,7 +397,7 @@ malloc_elem_free(struct malloc_elem *elem) >> >> memset(ptr, 0, data_len); >> >> - return 0; >> + return elem; >> } >> >> /* > > An explanation about why this change is needed would make sense I think. > > Thanks, > Olivier > Sure, i'll add this in future commits. However, to provide some context - we need this because down the line we will need to know which element did we create/free to be able to roll back the changes, should the sync fail. -- Thanks, Anatoly