From: "Liu, Jijiang" <jijiang.liu@intel.com>
To: Matt Laswell <laswell@infiniteio.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [dpdk-dev] Ability to/impact of running with smaller page sizes
Date: Tue, 1 Jul 2014 08:56:43 +0000 [thread overview]
Message-ID: <1ED644BD7E0A5F4091CF203DAFB8E4CC01D3D561@SHSMSX101.ccr.corp.intel.com> (raw)
In-Reply-To: <20140630234229.GA19646@plxv1142.pdx.intel.com>
Hi Matt,
On Mon, Jun 30, 2014 at 05:43:39PM -0500, Matt Laswell wrote:
> Hey Folks,
>
> In my application, I'm seeing some design considerations in a project
> I'm working on that push me towards the use of smaller memory page
> sizes. I'm curious - is it possible in practical terms to run DPDK without hugepages?
> If so, does anybody have any practical experience (or a
> back-of-the-envelop estimate) of how badly such a configuration would
> hurt performance? For sake of argument, assume that virtually all of
> the memory being used is in pre-allocated mempools (e.g lots of
> rte_mempool_create(), very little rte_malloc().
>
There is an case to run DPDK without hugepages in DPDK source codes, which is DPDK supports Xen Dom0. for this, we developed a dom0_mm driver.
Except for Xen Dom0, it is impossible to run DPDK without hugepages without any changes at memory initialization phase, but current rte_memzone_reserve_bounded() and
rte_mempool_xmem_create() implemention have already support non-hugepage usage in DPDK.
Thanks,
Jeff
next prev parent reply other threads:[~2014-07-01 8:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-30 22:43 Matt Laswell
2014-06-30 23:42 ` Jeff Shaw
2014-07-01 8:56 ` Liu, Jijiang [this message]
2014-07-01 11:06 ` Ananyev, Konstantin
2014-07-01 11:51 ` Burakov, Anatoly
2014-07-01 12:36 ` Matt Laswell
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=1ED644BD7E0A5F4091CF203DAFB8E4CC01D3D561@SHSMSX101.ccr.corp.intel.com \
--to=jijiang.liu@intel.com \
--cc=dev@dpdk.org \
--cc=laswell@infiniteio.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).