From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <dev-bounces@dpdk.org> Received: from dpdk.org (dpdk.org [92.243.14.124]) by dpdk.space (Postfix) with ESMTP id EA7AAA05D3 for <public@inbox.dpdk.org>; Fri, 26 Apr 2019 15:46:08 +0200 (CEST) Received: from [92.243.14.124] (localhost [127.0.0.1]) by dpdk.org (Postfix) with ESMTP id 101941B675; Fri, 26 Apr 2019 15:46:07 +0200 (CEST) Received: from mga05.intel.com (mga05.intel.com [192.55.52.43]) by dpdk.org (Postfix) with ESMTP id 13C8A1B119 for <dev@dpdk.org>; Fri, 26 Apr 2019 15:46:04 +0200 (CEST) X-Amp-Result: SKIPPED(no attachment in message) X-Amp-File-Uploaded: False Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga105.fm.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 26 Apr 2019 06:46:03 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.60,397,1549958400"; d="scan'208";a="153986552" Received: from aburakov-mobl1.ger.corp.intel.com (HELO [10.251.92.20]) ([10.251.92.20]) by orsmga002.jf.intel.com with ESMTP; 26 Apr 2019 06:46:02 -0700 To: "Suanming.Mou" <mousuanming@huawei.com>, "Varghese, Vipin" <vipin.varghese@intel.com>, "Pattan, Reshma" <reshma.pattan@intel.com> Cc: "'dev@dpdk.org'" <dev@dpdk.org> References: <1556210141-43153-1-git-send-email-mousuanming@huawei.com> <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D33DEB0@BGSMSX101.gar.corp.intel.com> <25e85f37-231e-d303-8d7a-e3addd6534d5@huawei.com> <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D33E2C8@BGSMSX101.gar.corp.intel.com> <4C9E0AB70F954A408CC4ADDBF0F8FA7D4D33E2E3@BGSMSX101.gar.corp.intel.com> <ee413010-8b73-c1e0-90b7-98586af2f94b@huawei.com> From: "Burakov, Anatoly" <anatoly.burakov@intel.com> Message-ID: <f4e09994-edb1-9a1d-70ed-74299edc93c0@intel.com> Date: Fri, 26 Apr 2019 14:46:01 +0100 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.6.1 MIME-Version: 1.0 In-Reply-To: <ee413010-8b73-c1e0-90b7-98586af2f94b@huawei.com> Content-Type: text/plain; charset="UTF-8"; format="flowed" Content-Language: en-US Content-Transfer-Encoding: 8bit Subject: Re: [dpdk-dev] [PATCH] app/pdump: exits once primary app exited X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions <dev.dpdk.org> List-Unsubscribe: <https://mails.dpdk.org/options/dev>, <mailto:dev-request@dpdk.org?subject=unsubscribe> List-Archive: <http://mails.dpdk.org/archives/dev/> List-Post: <mailto:dev@dpdk.org> List-Help: <mailto:dev-request@dpdk.org?subject=help> List-Subscribe: <https://mails.dpdk.org/listinfo/dev>, <mailto:dev-request@dpdk.org?subject=subscribe> Errors-To: dev-bounces@dpdk.org Sender: "dev" <dev-bounces@dpdk.org> Message-ID: <20190426134601.4soEGkdEs5XMYDYSQWtMCjMcgROb5SCUnGnZ6g5k7-w@z> On 26-Apr-19 1:08 PM, Suanming.Mou wrote: > > On 2019/4/26 18:56, Varghese, Vipin wrote: >> >> I will leave this suggestion open for comments from the maintainer. >> > Hi, > > Thanks for your suggestion. I have also tried to add an slave core to > monitor the primary status this afternoon. It works. > > I doubt if it can be add an new option as you suggested, but which will > also require people who complain the exiting to add an extra slave core > for that. > > Please waiting for the new patch in one or two days. > You can use alarm API to check for this regularly. It's not like the interrupt thread is doing much anyway. Just set alarm to fire every N seconds, and that's it. -- Thanks, Anatoly