DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Richardson, Bruce" <bruce.richardson@intel.com>
To: Mario Gianni <m.gianni@engineer.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Cannot mmap device resource in DPDK 1.7.0 multi-process/multi-thread
Date: Tue, 28 Oct 2014 12:19:10 +0000	[thread overview]
Message-ID: <59AF69C657FD0841A61C55336867B5B03443434C@IRSMSX103.ger.corp.intel.com> (raw)
In-Reply-To: <trinity-94da20ae-716e-488a-9588-4d3452f4c79c-1414162982295@3capp-mailcom-lxa11>

> -----Original Message-----
> From: Mario Gianni [mailto:m.gianni@engineer.com]
> Sent: Friday, October 24, 2014 4:03 PM
> To: Richardson, Bruce
> Cc: dev@dpdk.org
> Subject: Re: [dpdk-dev] Cannot mmap device resource in DPDK 1.7.0 multi-
> process/multi-thread
> 
> So you are telling me that in order to implement multi-process I should better
> use the l2fwd_fork example instead of client_server_mp.
> In fact if I use the client_server_mp with a lot of mp_client threads it gives me
> the error.
> If instead I use the l2fwd_fork example it doesn't give me the error.
> 
> One more question at this point:
> Assume that I use l2fwd_fork, when I launch the secondary process, how do I
> assign the lcore coremask associated with that process?
> 

With the l2fwd_fork example, the forked processes are not secondary proceses in the sense of the other DPDK multiprocess models - with each one having its own core mask and set of threads. Instead, each forked process is a single thread based off the core-mask provided at process startup. It's a different way of doing things, but one which provides separate processes, while guaranteeing that all processes can share the same hugepage memory at the same address without relying on having the kernel map things at specific points in the address space.

/Bruce

      reply	other threads:[~2014-10-28 12:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24 11:21 Mario Gianni
2014-10-24 12:08 ` Bruce Richardson
2014-10-24 13:04   ` Mario Gianni
2014-10-24 13:39     ` Bruce Richardson
2014-10-24 15:03       ` Mario Gianni
2014-10-28 12:19         ` Richardson, Bruce [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=59AF69C657FD0841A61C55336867B5B03443434C@IRSMSX103.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=m.gianni@engineer.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).