From: Oza Oza <oza.oza at broadcom.com>
To: spdk@lists.01.org
Subject: [SPDK] No free hugepages reported in hugepages
Date: Wed, 19 Jul 2017 14:02:47 +0530 [thread overview]
Message-ID: <528eb21edefd74f6dca93c727c3dab1f@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1017 bytes --]
Hi All,
1) DPDK fails if huge-pages are not reserved. But should not it fall
back to regular 4k pages ?
2) And how user space should know the requirement of number of hug
pages before-hand ?
a. Rather should it always be reserved before-hand in the system?,
with that we might waste some.
root(a)bcm958742t:~# /usr/share/spdk/examples/nvme/perf -r 'trtype:PCIe
traddr:0000:01:00.0' -q 128 -s 4096 -w write -d 2048 -t 30 -c 0x1
Starting DPDK 16.11.1 initialization...
[ DPDK EAL parameters: perf -c 1 -m 2048 --file-prefix=spdk_pid3[
187.734815] audit: type=1701 audit(1500448013.777:3): auid=4294967295 uid=0
gid=0 ses=4294967295 pid=3465 comm="perf"
exe="/usr/share/spdk/examples/nvme/perf" sig=6 res=1
465 ]
EAL: Detected 8 lcore(s)
EAL: No free hugepages reported in hugepages-2048kB
PANIC in rte_eal_init():
Cannot get hugepage information
1: [/usr/share/spdk/examples/nvme/perf() [0x4197d4]]
Aborted (core dumped)
Regards,
Oza.
[-- Attachment #2: attachment.html --]
[-- Type: text/html, Size: 4580 bytes --]
next reply other threads:[~2017-07-19 8:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-19 8:32 Oza Oza [this message]
-- strict thread matches above, loose matches on Subject: below --
2017-07-19 22:12 [SPDK] No free hugepages reported in hugepages Walker, Benjamin
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=528eb21edefd74f6dca93c727c3dab1f@mail.gmail.com \
--to=spdk@lists.01.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