From: Aniraj Kesavan <anirajkesavan@gmail.com>
To: Muhammad Zain-ul-Abideen <zain2294@gmail.com>
Cc: Andriy Berestovskyy <aber@semihalf.com>, users <users@dpdk.org>
Subject: Re: [dpdk-users] Need help understanding rte_eth_dev_count
Date: Thu, 13 Oct 2016 00:12:29 -0600 [thread overview]
Message-ID: <CAFOf+QV4t0EuZkcX+s4vc78ebZGtY_D2-7yqCjNf66pp0r54wg@mail.gmail.com> (raw)
In-Reply-To: <CAN7yQ2rQCNas06-YXGgO1ppxUQfKdu8BZSd=FrHVLFN5NTd86g@mail.gmail.com>
I have 1GB hugepages enabled and mounted, in fact I had traced through gdb
to find out that hugepage_init succeeds.
Or is it necessary to have 2MB hugepages in particular?
One thing I did notice is that I wasn't unbinding the devices properly. I
had to do them manually writing pci device ids to unbind location. Even
after that, I'm finding issues.
I also figured out that since I was building as a shared library, I needed
to pass -d <lib location> as a command line parameter. Even after doing
that, I'm getting the same errors.
On Thu, Oct 13, 2016 at 12:01 AM, Muhammad Zain-ul-Abideen <
zain2294@gmail.com> wrote:
> *"EAL: No free hugepages reported in hugepages-2048kB" *
> No huge pages are available, kindly restart your server, and re do the
> installation, plus tell me where the huge pages are being made.
> and if this is a valid address in ur case
> "*/sys/devices/system/node/node0/hugepages/hugepages-2048kB/nr_hugepages*"
>
--
Aniraj Kesavan
MS CS '15-'17,
University Of Utah
CS '08-'12,
Govt. Model Engineering College
alternate e-mail:anirajkalathel@gmail.com
http://www.cs.utah.edu/~aniraj/
next prev parent reply other threads:[~2016-10-13 6:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-12 4:44 Aniraj Kesavan
[not found] ` <CAOysbxpmme2xHxi5SVUi1ZO3KDz+jWvsu_7b_AmMmXNHrkRO3g@mail.gmail.com>
2016-10-12 17:47 ` Aniraj Kesavan
2016-10-13 6:01 ` Muhammad Zain-ul-Abideen
2016-10-13 6:12 ` Aniraj Kesavan [this message]
2016-10-13 6:17 ` Muhammad Zain-ul-Abideen
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=CAFOf+QV4t0EuZkcX+s4vc78ebZGtY_D2-7yqCjNf66pp0r54wg@mail.gmail.com \
--to=anirajkesavan@gmail.com \
--cc=aber@semihalf.com \
--cc=users@dpdk.org \
--cc=zain2294@gmail.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).