DPDK usage discussions
 help / color / mirror / Atom feed
From: 曾懷恩 <the@csie.io>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: users@dpdk.org
Subject: Re: [dpdk-users] segmentation fault after using rte_malloc()
Date: Fri, 19 Apr 2019 11:31:27 +0800	[thread overview]
Message-ID: <AF5A48F2-5EA3-4CF3-BFAE-B393D04D1616@csie.io> (raw)
In-Reply-To: <20190418195944.04c4cec5@hermes.lan>

HI, Stephen,

Yes, I set huge page in  default_hugepagesz=1G hugepagesz=1G hugepages=4

and also did rte_eal_init at the beginning of my program.

thanks for reply.


> Stephen Hemminger <stephen@networkplumber.org> 於 2019年4月19日 上午10:59 寫道：
> 
> On Fri, 19 Apr 2019 09:11:05 +0800
> 曾懷恩 <the@csie.io> wrote:
> 
>> 	Hi all, 
>> 
>> 	i have 1 problem while using rte_malloc
>> 
>> 	Every time I use this function and use the memory it returns, it shows segmentation fault(core dump)
>> 
>> 	Is something wrong?
>> 
>> 	thanks.
>> 
>> 
>> 	rte init …
>> 	………...
>> 	unsigned char *str1;
>> 	printf("str1 addr = %x\n", str1);
>> 	str1 = rte_malloc(NULL,2,RTE_CACHE_LINE_SIZE);
>> 	printf("str1 addr = %x\n", str1);
>> 	str1[0] = 'a’; //segmentation fault here
>> 	str1[1] = '\0';
> Do you have huge pages?
> Did you do eal_init?


  reply	other threads:[~2019-04-19  3:31 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-19  1:11 曾懷恩
2019-04-19  2:59 ` Stephen Hemminger
2019-04-19  3:31   ` 曾懷恩 [this message]
2019-04-20 20:29     ` Wiles, Keith
2019-04-22  6:43       ` 曾懷恩
2019-04-22 13:09         ` Wiles, Keith
2019-04-23 17:34           ` 曾懷恩
2019-04-24 14:22             ` 曾懷恩
2019-04-24 14:38               ` Wiles, Keith
2019-04-25  3:55                 ` 曾懷恩
2019-04-25  4:18                   ` Wiles, Keith
2020-07-24  4:07 Logan Von

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=AF5A48F2-5EA3-4CF3-BFAE-B393D04D1616@csie.io \
    --to=the@csie.io \
    --cc=stephen@networkplumber.org \
    --cc=users@dpdk.org \
    /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).