From: Wang Sheng-Hui <shhuiw@gmail.com>
To: dev@dpdk.org
Subject: [dpdk-dev] [PATCH] eal_lcore.c: print the supported maximum lcores as configured, and detected lcores on eal cpu init
Date: Mon, 14 Apr 2014 13:37:04 +0800 [thread overview]
Message-ID: <534B7400.3050905@gmail.com> (raw)
Print the maximum lcore(s) as configured, and the number of lcore(s) detected
on eal cpu init as debug info besides the not separate detected/not-detected
lcore info.
Signed-off-by: Wang Sheng-Hui <shhuiw@gmail.com>
---
lib/librte_eal/linuxapp/eal/eal_lcore.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/lib/librte_eal/linuxapp/eal/eal_lcore.c b/lib/librte_eal/linuxapp/eal/eal_lcore.c
index d310d85..da20fa3 100644
--- a/lib/librte_eal/linuxapp/eal/eal_lcore.c
+++ b/lib/librte_eal/linuxapp/eal/eal_lcore.c
@@ -182,6 +182,9 @@ rte_eal_cpu_init(void)
}
/* Set the count of enabled logical cores of the EAL configuration */
config->lcore_count = count;
+ RTE_LOG(DEBUG, EAL, "Support Maximum %u Logical Core(s) by configuration.\n",
+ RTE_MAX_LCORE);
+ RTE_LOG(DEBUG, EAL, "Detected %u lcore(s)\n", config->lcore_count);
return 0;
}
--
1.8.3.2
next reply other threads:[~2014-04-14 5:37 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-14 5:37 Wang Sheng-Hui [this message]
2014-05-05 16:09 ` Thomas Monjalon
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=534B7400.3050905@gmail.com \
--to=shhuiw@gmail.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).