From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 574] get_num_hugepages_on_node() doesn't mention which node doesn't have free hugepages
Date: Tue, 10 Nov 2020 14:41:38 +0000 [thread overview]
Message-ID: <bug-574-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=574
Bug ID: 574
Summary: get_num_hugepages_on_node() doesn't mention which node
doesn't have free hugepages
Product: DPDK
Version: 20.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: enhancement
Priority: Normal
Component: core
Assignee: dev@dpdk.org
Reporter: michallinuxstuff@gmail.com
Target Milestone: ---
In case free_hugepages under nodeN reads 0 the following LOG is being
generated:
> EAL: No free hugepages reported in hugepages-2048kB
However, this doesn't say exactly under which node there's no free hugepages.
It would be nice if the above log included the socket|node id. Something along
the lines of:
> `EAL: No free hugepages reported in hugepages-2048kB (Node0)`
or similar. :)
--
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2020-11-10 14:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-10 14:41 bugzilla [this message]
2021-01-20 17:16 ` [dpdk-dev] [Bug 574] get_num_hugepages_on_node() doesn't mention which node doesn't have free hugepages bugzilla
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=bug-574-3@http.bugs.dpdk.org/ \
--to=bugzilla@dpdk.org \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.