DPDK patches and discussions
 help / color / mirror / Atom feed
From: Sergio Gonzalez Monroy <sergio.gonzalez.monroy@intel.com>
To: Mahdi Moradmand Badie <mahdi.mbadie@gmail.com>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] rte_malloc
Date: Wed, 11 May 2016 11:29:27 +0100	[thread overview]
Message-ID: <7b0f6538-c5b0-3ec0-9e27-e965c35e10f0@intel.com> (raw)
In-Reply-To: <CAM=H7wd9xh2Sv2cf0o=DqgAycOtXBaOWzG-7ziTaFCGnGesAZg@mail.gmail.com>

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 
> <sergio.gonzalez.monroy@intel.com 
> <mailto:sergio.gonzalez.monroy@intel.com>> 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
>>     <sergio.gonzalez.monroy@intel.com
>>     <mailto:sergio.gonzalez.monroy@intel.com>> 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
>>>         <sergio.gonzalez.monroy@intel.com
>>>         <mailto:sergio.gonzalez.monroy@intel.com>> 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
>>>                 <http://dpdk.org/doc/api/rte__malloc_8h.html#afb7316a4ec228ed9b8ffc1864b03d85b>
>>>                 (sizeof(*p)); ==>
>>>                 struct lcore_params *p = rte_malloc
>>>                 <http://dpdk.org/doc/api/rte__malloc_8h.html#afb7316a4ec228ed9b8ffc1864b03d85b>(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

      reply	other threads:[~2016-05-11 10:29 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-09 17:32 Mahdi Moradmand Badie
2016-05-10  8:12 ` Sergio Gonzalez Monroy
2016-05-10 15:15   ` Mahdi Moradmand Badie
2016-05-10 15:17   ` Mahdi Moradmand Badie
2016-05-10 15:31     ` Sergio Gonzalez Monroy
2016-05-10 15:55       ` Mahdi Moradmand Badie
2016-05-10 16:12         ` Sergio Gonzalez Monroy
2016-05-10 16:13           ` Mahdi Moradmand Badie
2016-05-11 10:29             ` Sergio Gonzalez Monroy [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=7b0f6538-c5b0-3ec0-9e27-e965c35e10f0@intel.com \
    --to=sergio.gonzalez.monroy@intel.com \
    --cc=dev@dpdk.org \
    --cc=mahdi.mbadie@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).