From: bugzilla@dpdk.org
To: dev@dpdk.org
Subject: [dpdk-dev] [Bug 336] Unable to exit DPDK application when running as separate thread.
Date: Mon, 05 Aug 2019 07:53:22 +0000 [thread overview]
Message-ID: <bug-336-3@http.bugs.dpdk.org/> (raw)
https://bugs.dpdk.org/show_bug.cgi?id=336
Bug ID: 336
Summary: Unable to exit DPDK application when running as
separate thread.
Product: DPDK
Version: 17.11
Hardware: All
OS: All
Status: UNCONFIRMED
Severity: normal
Priority: Normal
Component: other
Assignee: dev@dpdk.org
Reporter: ullas-d.bhat@hpe.com
Target Milestone: ---
We have written application where EAL initialization and resource allocation
done in main program. Then we are launching/calling a function below
code(Reference 1).Launched Function is responsible for creating thread and
perform corresponding job,but we see that after thread completes it's job we
are not able to exit from application it gets hanged.
And we are seeing newly created thread unable to access lcore value as accessed
by main thread.
using below function
rte_lcore_id()
Below is command used to run application.
#./<executable file> -l 1-2 -d /usr/local/lib/librte_pmd_e1000.so.1.1 -w
0000:04:00.1 -w 0000:04:00.2
Also whatever statement/code written after below code is not executed in main
thread.
Reference 1: Code to launch function in main program.
________________________________________
rte_eal_mp_remote_launch(<function_name>,NULL, CALL_MASTER);
RTE_LCORE_FOREACH_SLAVE(lcore) {
if(rte_eal_wait_lcore(lcore) < 0 ) {
return -1;
}
}
can you please guide us what is the correct procedure to run DPDK application
as separate thread/Tell us what is the mistake we are doing?.
Thanks & Regards,
ullas
--
You are receiving this mail because:
You are the assignee for the bug.
reply other threads:[~2019-08-05 7:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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-336-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 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).