DPDK usage discussions
 help / color / mirror / Atom feed
From: tom.barbette@ulg.ac.be
To: "Tan, Jianfeng" <jianfeng.tan@intel.com>
Cc: users@dpdk.org, "Gonzalez Monroy,
	Sergio" <sergio.gonzalez.monroy@intel.com>
Subject: Re: [dpdk-users] Secondary process try to map hugepage even with	--no-huge
Date: Thu, 6 Jul 2017 10:06:22 +0200 (CEST)	[thread overview]
Message-ID: <249213765.27102242.1499328382234.JavaMail.zimbra@ulg.ac.be> (raw)
In-Reply-To: <ED26CBA2FAD1BF48A8719AEF02201E365122673E@SHSMSX103.ccr.corp.intel.com>

Thanks for your prompt answer. Are there any plan to change that behavior, like using shm memory if no-huge is there? As I said, this would be very useful for testing.

Thanks,
Tom

----- Mail original -----
> De: "Tan, Jianfeng" <jianfeng.tan@intel.com>
> À: "tom barbette" <tom.barbette@ulg.ac.be>, users@dpdk.org
> Cc: "Gonzalez Monroy, Sergio" <sergio.gonzalez.monroy@intel.com>
> Envoyé: Jeudi 6 Juillet 2017 04:46:02
> Objet: RE: [dpdk-users] Secondary process try to map hugepage even with	--no-huge

> Hi,
> 
>> -----Original Message-----
>> From: users [mailto:users-bounces@dpdk.org] On Behalf Of
>> tom.barbette@ulg.ac.be
>> Sent: Wednesday, July 5, 2017 9:58 PM
>> To: users@dpdk.org
>> Cc: Gonzalez Monroy, Sergio
>> Subject: [dpdk-users] Secondary process try to map hugepage even with --
>> no-huge
>> 
>> Hi list,
>> 
>> I've got a primary/secondary application that works with huge pages enabled
>> but not with "--no-huge". The secondary application try to
>> access .rte_hugepage_info no matter the "--no-huge" being passed to both
>> master and slave.
> 
> So far if --no-huge is used, we are mmap anonymous memory, which makes it not
> possible to share the memory with secondary (always refer to a config file,
> open and mmap to the same addr).
> 
> And we did not write anything into config file if we use --no-huge. This is a
> limitation for now.
> 
>> 
>> This is especially important for functional regression test where I cannot use
>> huge pages or sudo (like Travis, Gitlab CI, ...)
>> 
>> Trying with the simple_mp example :
>>  ./simple_mp --no-huge -m 128MB --proc-type=secondary --
>> EAL: Detected 8 lcore(s)
>> EAL: Probing VFIO support...
>> EAL: Could not mmap /home/tom/.rte_hugepage_info
>> PANIC in rte_eal_init():
>> Cannot init memory
>> 6: [./simple_mp(_start+0x2a) [0x43512a]]
>> 5: [/lib64/libc.so.6(__libc_start_main+0xf1) [0x7ffff6ed4401]]
>> 4: [./simple_mp(main+0x6) [0x4347b6]]
>> 3: [./simple_mp(rte_eal_init+0xe90) [0x46e2d0]]
>> 2: [./simple_mp(__rte_panic+0xbe) [0x4301ab]]
>> 1: [./simple_mp(rte_dump_stack+0x16) [0x475c06]]
>> zsh: abort (core dumped)  ./simple_mp --no-huge --proc-type=secondary --
>> 
>> 
>> With sudo, I get a little further, I guess this is not the problem.
>> EAL: Could not mmap /dev/hugepages/rtemap_53
>> PANIC in rte_eal_init():
>> 
>> Thanks,
>> 
> > Tom

      reply	other threads:[~2017-07-06  8:06 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-05 13:57 tom.barbette
2017-07-06  2:46 ` Tan, Jianfeng
2017-07-06  8:06   ` tom.barbette [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=249213765.27102242.1499328382234.JavaMail.zimbra@ulg.ac.be \
    --to=tom.barbette@ulg.ac.be \
    --cc=jianfeng.tan@intel.com \
    --cc=sergio.gonzalez.monroy@intel.com \
    --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).