From: Hemant Agrawal <hemant.agrawal@nxp.com>
To: dev@dpdk.org
Cc: Hemant Agrawal <hemant.agrawal@nxp.com>
Subject: [dpdk-dev] [PATCH] tailq: secondary process may not have all tailq available
Date: Thu, 14 Jan 2021 12:43:46 +0530 [thread overview]
Message-ID: <20210114071346.18235-1-hemant.agrawal@nxp.com> (raw)
Secondary process may not have all the tailq available for
mapping, so better to ignore the error.
e.g. if the primary process is linked with N libs
and secondary process is linked with less number of libs.
dpdk-procinfo results into following error:
EAL: Cannot initialize tailq: VMBUS_RESOURCE_LIST
Signed-off-by: Hemant Agrawal <hemant.agrawal@nxp.com>
---
lib/librte_eal/common/eal_common_tailqs.c | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/lib/librte_eal/common/eal_common_tailqs.c b/lib/librte_eal/common/eal_common_tailqs.c
index ead06897b8..55bfc70db4 100644
--- a/lib/librte_eal/common/eal_common_tailqs.c
+++ b/lib/librte_eal/common/eal_common_tailqs.c
@@ -155,7 +155,8 @@ rte_eal_tailqs_init(void)
/* second part of register job for "early" tailqs, see
* rte_eal_tailq_register and EAL_REGISTER_TAILQ */
rte_eal_tailq_update(t);
- if (t->head == NULL) {
+ if (t->head == NULL &&
+ rte_eal_process_type() == RTE_PROC_PRIMARY) {
RTE_LOG(ERR, EAL,
"Cannot initialize tailq: %s\n", t->name);
/* TAILQ_REMOVE not needed, error is already fatal */
--
2.17.1
next reply other threads:[~2021-01-14 7:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-14 7:13 Hemant Agrawal [this message]
2021-01-14 13:44 ` David Marchand
2021-01-18 5:55 ` Hemant Agrawal
2021-03-25 14:16 ` David Marchand
2021-03-25 16:05 ` Stephen Hemminger
2021-03-25 16:14 ` Bruce Richardson
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=20210114071346.18235-1-hemant.agrawal@nxp.com \
--to=hemant.agrawal@nxp.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).