From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga14.intel.com (mga14.intel.com [192.55.52.115]) by dpdk.org (Postfix) with ESMTP id 7513791F1 for ; Tue, 26 Jan 2016 10:04:31 +0100 (CET) Received: from fmsmga002.fm.intel.com ([10.253.24.26]) by fmsmga103.fm.intel.com with ESMTP; 26 Jan 2016 01:04:30 -0800 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.22,349,1449561600"; d="scan'208";a="901260852" Received: from irsmsx154.ger.corp.intel.com ([163.33.192.96]) by fmsmga002.fm.intel.com with ESMTP; 26 Jan 2016 01:04:29 -0800 Received: from irsmsx112.ger.corp.intel.com (10.108.20.5) by IRSMSX154.ger.corp.intel.com (163.33.192.96) with Microsoft SMTP Server (TLS) id 14.3.248.2; Tue, 26 Jan 2016 09:04:28 +0000 Received: from irsmsx102.ger.corp.intel.com ([169.254.2.97]) by irsmsx112.ger.corp.intel.com ([169.254.1.159]) with mapi id 14.03.0248.002; Tue, 26 Jan 2016 09:04:28 +0000 From: "Van Haaren, Harry" To: "Qiu, Michael" , "david.marchand@6wind.com" Thread-Topic: [dpdk-dev] [PATCH] eal: add function to check if primary proc alive Thread-Index: AQHRU4YWhvADP+xDWU6YXyDiXb5ALp8NhuEw Date: Tue, 26 Jan 2016 09:04:28 +0000 Message-ID: References: <1453296322-1210-1-git-send-email-harry.van.haaren@intel.com> <533710CFB86FA344BFBF2D6802E6028622F2180B@SHSMSX101.ccr.corp.intel.com> <533710CFB86FA344BFBF2D6802E6028622F221CB@SHSMSX101.ccr.corp.intel.com> In-Reply-To: <533710CFB86FA344BFBF2D6802E6028622F221CB@SHSMSX101.ccr.corp.intel.com> Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: x-titus-metadata-40: eyJDYXRlZ29yeUxhYmVscyI6IiIsIk1ldGFkYXRhIjp7Im5zIjoiaHR0cDpcL1wvd3d3LnRpdHVzLmNvbVwvbnNcL0ludGVsMyIsImlkIjoiNjM2NmUxZjgtNGMyMi00MTlkLTliNDQtYTFiNmQwODVlODg5IiwicHJvcHMiOlt7Im4iOiJDVFBDbGFzc2lmaWNhdGlvbiIsInZhbHMiOlt7InZhbHVlIjoiQ1RQX1BVQkxJQyJ9XX1dfSwiU3ViamVjdExhYmVscyI6W10sIlRNQ1ZlcnNpb24iOiIxNS40LjEwLjE5IiwiVHJ1c3RlZExhYmVsSGFzaCI6IkRCaUpxeGVHK0h0RmNvaFdocVR5RlZLeEJxTnM0QzJFOHNDeU9QN0VMY0k9In0= x-ctpclassification: CTP_PUBLIC x-originating-ip: [163.33.239.180] Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 Cc: "dev@dpdk.org" Subject: Re: [dpdk-dev] [PATCH] eal: add function to check if primary proc alive X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 26 Jan 2016 09:04:31 -0000 > From: Qiu, Michael > On 1/25/2016 7:51 PM, Van Haaren, Harry wrote: > > Not really, the secondary process will need some CPU, > > however it can sleep so it doesn't have to use 100% of it. > > It shouldn't be run on a core that is used by the primary > > for packet-forwarding though - that will impact performance. >=20 > If not, what will happen if the primary been killed after you check > alive? At that time, the secondary may be doing some work need primary > alive. What work are you thinking of? Apart from the shared config and hugepages, primary and secondary processes are running in their own address-space, and if the primary gets killed, the secondary will notice when it next polls rte_eal_primary_proc_alive(). Whatever work the secondary was performing (in its own address space) won't be directly changed by the primary being killed, because the shared config and hugepages stay (EAL "cleans up" when the primary is re-launched, not on quit). -Harry