DPDK patches and discussions
 help / color / mirror / Atom feed
From: "Choi, Sy Jong" <sy.jong.choi@intel.com>
To: Alex Markuze <alex@weka.io>, "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Huge Pages.
Date: Wed, 1 Oct 2014 09:28:43 +0000	[thread overview]
Message-ID: <697F8B1B48670548A5BAB03E8283550F2D52826C@PGSMSX107.gar.corp.intel.com> (raw)
In-Reply-To: <CAKfHP0Um4AOxqYfZTAATmFhwzZbzcq+Nag7_ovXXbkmPwHuLWQ@mail.gmail.com>

Hi Alex,

There option in EAL when you starts DPDK where by configure the amount of memory consume by DPDK.
• -m MB
	Memory to allocate. See also --socket-mem.

• --socket-mem
	Set the memory to allocate on specific sockets (use comma separated values).

Regards,
Choi, Sy Jong
Platform Application Engineer


-----Original Message-----
From: dev [mailto:dev-bounces@dpdk.org] On Behalf Of Alex Markuze
Sent: Wednesday, October 01, 2014 5:21 PM
To: dev@dpdk.org
Subject: [dpdk-dev] Huge Pages.

Hi,
How well does DPDK play with other applications using huge pages?
Looking at eal_init/eal_hugepage_info_init it seems that DPDK will try to grab All available huge pages.

Is there an existing way to limit the number of huge pages taken ?
My goal is to be able to run several applications each with its own dpdk instance and a possible 3rd party application all using huge pages. Is this possible under DPDKs current design?

Sharing the NICs is fairly simple if we specify the available lci functions per dpdk instance but at first glance sharing huge pages looks like a problem.

Thanks.

  reply	other threads:[~2014-10-01  9:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-01  9:21 Alex Markuze
2014-10-01  9:28 ` Choi, Sy Jong [this message]
2014-10-01  9:30 ` Bruce Richardson

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=697F8B1B48670548A5BAB03E8283550F2D52826C@PGSMSX107.gar.corp.intel.com \
    --to=sy.jong.choi@intel.com \
    --cc=alex@weka.io \
    --cc=dev@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).