DPDK patches and discussions
 help / color / mirror / Atom feed
From: Matt Laswell <laswell@infiniteio.com>
To: dev@dpdk.org
Subject: [dpdk-dev] Ability to/impact of running with smaller page sizes
Date: Mon, 30 Jun 2014 17:43:39 -0500	[thread overview]
Message-ID: <CA+GnqAo_mytb7A=HQ7BY+XRyczazd4fpt_wTvj_R8-Zde3wGhw@mail.gmail.com> (raw)

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().

Thanks in advance for your help.

-- 
Matt Laswell

             reply	other threads:[~2014-06-30 22:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-30 22:43 Matt Laswell [this message]
2014-06-30 23:42 ` Jeff Shaw
2014-07-01  8:56   ` Liu, Jijiang
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='CA+GnqAo_mytb7A=HQ7BY+XRyczazd4fpt_wTvj_R8-Zde3wGhw@mail.gmail.com' \
    --to=laswell@infiniteio.com \
    --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).