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 C98CBC428 for ; Wed, 11 May 2016 12:29:29 +0200 (CEST) Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga103.jf.intel.com with ESMTP; 11 May 2016 03:29:28 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.24,608,1455004800"; d="scan'208,217";a="973372120" Received: from smonroyx-mobl.ger.corp.intel.com (HELO [10.237.220.195]) ([10.237.220.195]) by orsmga002.jf.intel.com with ESMTP; 11 May 2016 03:29:28 -0700 From: Sergio Gonzalez Monroy To: Mahdi Moradmand Badie Cc: dev@dpdk.org References: <6cbfe6bd-b4c4-c0c8-3969-9d362193d8b3@intel.com> <2de4ef85-cdd0-9cd8-f1ff-20f81930a258@intel.com> Message-ID: <7b0f6538-c5b0-3ec0-9e27-e965c35e10f0@intel.com> Date: Wed, 11 May 2016 11:29:27 +0100 User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Content-Filtered-By: Mailman/MimeDel 2.1.15 Subject: Re: [dpdk-dev] rte_malloc X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 11 May 2016 10:29:30 -0000 Ok. So if you build DPDK from the sources, you would have an 'app' directory in you build directory. You can read the Getting Started Guide for more info: http://dpdk.readthedocs.io/en/v16.04/linux_gsg/index.html Once you ran the 'test' DPDK application (located inside the 'app' directory) you would get a shell where you can run different kind of autotests/tests. One of them is the 'malloc_autotest'. Let me know the result of running that test. Sergio On 10/05/2016 17:13, Mahdi Moradmand Badie wrote: > No, I don't have any idea? :) > > On 10 May 2016 at 12:12, Sergio Gonzalez Monroy > > wrote: > > Have you tried to run the unit tests? (Run 'app/test' application, > then 'malloc_autotest') > > Sergio > > > On 10/05/2016 16:55, Mahdi Moradmand Badie wrote: >> #!/bin/sh >> ./build/app/Mahdi_test -c 0x55 --master-lcore 0 >> >> On 10 May 2016 at 11:31, Sergio Gonzalez Monroy >> > > wrote: >> >> Forgot to ask, >> >> What's the command line you are using to run the app? >> >> Sergio >> >> >> On 10/05/2016 16:17, Mahdi Moradmand Badie wrote: >>> Thanks Sergio, >>> Yes sure, >>> I attached files, it seems so easy but doesn't work. >>> Thanks, >>> >>> On 10 May 2016 at 04:12, Sergio Gonzalez Monroy >>> >> > wrote: >>> >>> Hi, >>> >>> On 09/05/2016 18:32, Mahdi Moradmand Badie wrote: >>> >>> Hello All, >>> >>> I had a problem regarding use the rte_malloc. >>> I want to know if I want to use rte_malloc instead >>> of malloc just mak >>> change like this >>> struct lcore_params *p = malloc >>> >>> (sizeof(*p)); ==> >>> struct lcore_params *p = rte_malloc >>> (NULL, >>> sizeof(*p), 0); >>> is enough ? >>> >>> >>> Yes, malloc(sizeof(*p)) has an equivalent behavior to >>> rte_malloc(NULL, sizeof(*p), 0) >>> in the context of a DPDK application. >>> >>> Because I have problem and Segmentation fault (core >>> dumped) ?? >>> >>> >>> Could you provide more details of how to reproduce or >>> could you try to >>> reproduce your problem using a very simple example like >>> examples/helloworld ? >>> >>> Sergio >>> >>> Thanks in advance, >>> >>> >>> >>> >>> >>> >>> -- >>> M@hdi Mor@dm@nd B@die >> >> >> >> >> -- >> M@hdi Mor@dm@nd B@die > > > > > -- > M@hdi Mor@dm@nd B@die