From: Stephen Hemminger <stephen-OTpzqLSitTUnbdJkjeBofR2eb7JE58TQ@public.gmane.org>
To: Kamraan Nasim <knasim-LfGgLkH2qHaTtA8H5PvdGFaTQe2KTcn/@public.gmane.org>
Cc: dev-VfR2kkLFssw@public.gmane.org, liran-I7wstvAgZDk@public.gmane.org
Subject: Re: dev Digest, Vol 22, Issue 37
Date: Wed, 15 Apr 2015 17:50:31 -0700 [thread overview]
Message-ID: <20150415175031.44c9f082@urahara> (raw)
In-Reply-To: <CAPrTskgnK3XNZNkeTe_qC=yfy9O7gKpD1bY9=ckwOSx83xUyMQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Wed, 15 Apr 2015 17:43:02 -0700
Kamraan Nasim <knasim-LfGgLkH2qHaTtA8H5PvdGFaTQe2KTcn/@public.gmane.org> wrote:
> >
> > This had me stumped for a while as well. In my case, PostGres9.4 was also
> > running on my system which also used huge pages and came up before my DPDK
> > application causing rte_mempool_create() to ENOMEM.
>
>
> Check which other applications are using huge pages:
> > lsof | grep huge
>
> And see if you can disable huge pages for them or increase the total pages
> you're allocating in Kernel.
>
There are some libraries to allow for better cooperation with huge pages.
But DPDK development started in parallel and hasn't caught up to using them.
See
http://libhugetlbfs.sourceforge.net/
prev parent reply other threads:[~2015-04-16 0:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.9407.1420917966.2352.dev@dpdk.org>
[not found] ` <mailman.9407.1420917966.2352.dev-VfR2kkLFssw@public.gmane.org>
2015-04-16 0:43 ` dev Digest, Vol 22, Issue 37 Kamraan Nasim
[not found] ` <CAPrTskgnK3XNZNkeTe_qC=yfy9O7gKpD1bY9=ckwOSx83xUyMQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-04-16 0:50 ` Stephen Hemminger [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=20150415175031.44c9f082@urahara \
--to=stephen-otpzqlsittunbdjkjebofr2eb7je58tq@public.gmane.org \
--cc=dev-VfR2kkLFssw@public.gmane.org \
--cc=knasim-LfGgLkH2qHaTtA8H5PvdGFaTQe2KTcn/@public.gmane.org \
--cc=liran-I7wstvAgZDk@public.gmane.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).