DPDK usage discussions
 help / color / Atom feed
From: 曾懷恩 <the@csie.io>
To: "Wiles, Keith" <keith.wiles@intel.com>
Cc: Stephen Hemminger <stephen@networkplumber.org>,
	"users@dpdk.org" <users@dpdk.org>
Subject: Re: [dpdk-users] segmentation fault after using rte_malloc()
Date: Mon, 22 Apr 2019 14:43:19 +0800
Message-ID: <774EEFED-F56A-426E-93FA-92BF9584DD4E@csie.io> (raw)
In-Reply-To: <EFEE725A-2937-4095-91D2-9C01C6FDC611@intel.com>

Hi Wiles,

here is my sample code with just doing rte_eal_init() and rte_malloc() .

-------------- next part --------------
 
-------------- next part --------------


And my start eal cmdline option is ./build/test -l 0-1 -n 4

Thank you very much for your reply
> Wiles, Keith <keith.wiles@intel.com> ? 2019?4?21? ??4:29 ???
> 
> 
> 
> Sent from my iPhone
> 
>> On Apr 18, 2019, at 11:31 PM, ??? <the@csie.io> wrote:
>> 
>> 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.
> 
> Is the core doing the rte_malloc one of the cores listed in the core list on the command line.  In other words the pthread doing the allocation should be the master lcore or one of the slave lcores.
> 
> Also I seems like a very simple test case, can you do the rte_eal_init() and then do the allocation as your sample code looks and then exit? Does this cause a segfault?
>> 
>> 
>>> 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 index

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   ` 曾懷恩
2019-04-20 20:29     ` Wiles, Keith
2019-04-22  6:43       ` 曾懷恩 [this message]
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 publically 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=774EEFED-F56A-426E-93FA-92BF9584DD4E@csie.io \
    --to=the@csie.io \
    --cc=keith.wiles@intel.com \
    --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

DPDK usage discussions

Archives are clonable:
	git clone --mirror http://inbox.dpdk.org/users/0 users/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 users users/ http://inbox.dpdk.org/users \
		users@dpdk.org
	public-inbox-index users


Newsgroup available over NNTP:
	nntp://inbox.dpdk.org/inbox.dpdk.users


AGPL code for this site: git clone https://public-inbox.org/ public-inbox