From mboxrd@z Thu Jan 1 00:00:00 1970 From: santosh Subject: Re: [PATCH v2 13/41] eal: replace memseg with memseg lists Date: Sat, 24 Mar 2018 17:53:57 +0530 Message-ID: <568b60eb-60a8-8f9a-8b42-0d996cad1c2f@caviumnetworks.com> References: <495e60f4e02af8a344c0f817a60d1ee9b9322df4.1520428025.git.anatoly.burakov@intel.com> <15b7a198-2963-30e1-9d31-abbe01dd62d1@caviumnetworks.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit Cc: Thomas Monjalon , Yuanhan Liu , Maxime Coquelin , Tiwei Bie , keith.wiles@intel.com, jianfeng.tan@intel.com, andras.kovacs@ericsson.com, laszlo.vadkeri@ericsson.com, benjamin.walker@intel.com, bruce.richardson@intel.com, 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, olivier.matz@6wind.com To: "Burakov, Anatoly" , dev@dpdk.org Return-path: Received: from NAM02-BL2-obe.outbound.protection.outlook.com (mail-bl2nam02on0055.outbound.protection.outlook.com [104.47.38.55]) by dpdk.org (Postfix) with ESMTP id 29CB25F16 for ; Sat, 24 Mar 2018 13:24:25 +0100 (CET) In-Reply-To: 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 Saturday 24 March 2018 04:38 PM, Burakov, Anatoly wrote: > On 24-Mar-18 6:01 AM, santosh wrote: >> Hi Anatoly, >> >> Thanks for good work!. >> Few observations: >> # Noticed performance regression for thunderx platform for l3fwd application, >> drops by 3%. git bisect shows this changeset is offending commit. >> I'm still investigating reason for perf-dip.. >> Would like to know - have you noticed any regression on x86 platform? > > I haven't noticed any regressions on x86. Would it by any chance be due to the fact that memory segments are now non-contiguous or are allocated from smaller page sizes first? > > I am in the process of preparing a v3, which moves some things around and is better at git bisect (and fixes all compile issues i am or was made aware of). Does performance regression also happen in legacy mode? > Test ran for legacy mode only and noticed performance regression. Thanks. [..]