From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dpdk.org (dpdk.org [92.243.14.124]) by inbox.dpdk.org (Postfix) with ESMTP id C3401A00E6 for ; Mon, 5 Aug 2019 09:53:24 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id E9E681BE18; Mon, 5 Aug 2019 09:53:23 +0200 (CEST) Received: from inbox.dpdk.org (xvm-172-178.dc0.ghst.net [95.142.172.178]) by dpdk.org (Postfix) with ESMTP id DAAE41BE18 for ; Mon, 5 Aug 2019 09:53:22 +0200 (CEST) Received: by inbox.dpdk.org (Postfix, from userid 33) id 9CBDDA0613; Mon, 5 Aug 2019 09:53:22 +0200 (CEST) From: bugzilla@dpdk.org To: dev@dpdk.org Date: Mon, 05 Aug 2019 07:53:22 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: DPDK X-Bugzilla-Component: other X-Bugzilla-Version: 17.11 X-Bugzilla-Keywords: X-Bugzilla-Severity: normal X-Bugzilla-Who: ullas-d.bhat@hpe.com X-Bugzilla-Status: UNCONFIRMED X-Bugzilla-Resolution: X-Bugzilla-Priority: Normal X-Bugzilla-Assigned-To: dev@dpdk.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter target_milestone Message-ID: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: http://bugs.dpdk.org/ Auto-Submitted: auto-generated X-Auto-Response-Suppress: All MIME-Version: 1.0 Subject: [dpdk-dev] [Bug 336] Unable to exit DPDK application when running as separate thread. X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" https://bugs.dpdk.org/show_bug.cgi?id=3D336 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.=20 And we are seeing newly created thread unable to access lcore value as acce= ssed by main thread. using below function=20 rte_lcore_id() Below is command used to run application. #./ -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 ma= in thread. Reference 1: Code to launch function in main program.=20 ________________________________________ rte_eal_mp_remote_launch(,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 applicati= on as separate thread/Tell us what is the mistake we are doing?. Thanks & Regards, ullas --=20 You are receiving this mail because: You are the assignee for the bug.=