From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Monjalon Subject: Re: [PATCH v6] eal: add function to check if primary proc alive Date: Tue, 08 Mar 2016 12:13:50 +0100 Message-ID: <2251445.Z6GIcehbaX@xps13> References: <1457350669-32582-1-git-send-email-harry.van.haaren@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7Bit Cc: dev@dpdk.org To: "Van Haaren, Harry" Return-path: Received: from mail-wm0-f51.google.com (mail-wm0-f51.google.com [74.125.82.51]) by dpdk.org (Postfix) with ESMTP id C374B2C68 for ; Tue, 8 Mar 2016 12:15:28 +0100 (CET) Received: by mail-wm0-f51.google.com with SMTP id l68so145137144wml.0 for ; Tue, 08 Mar 2016 03:15:28 -0800 (PST) In-Reply-To: List-Id: patches and discussions about DPDK List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" 2016-03-08 09:58, Van Haaren, Harry: > From: David Marchand [mailto:david.marchand@6wind.com] > > When I look at this new api, I am under the impression that you are > > supposed to check for primary liveliness once dpdk init has finished > > (from your secondary process point of view), not before and not while > > it is initialising. > > The issue is that if a secondary process is initialized, it holds a read > lock on /var/run/.rte_config and this prevents a primary from starting. The new function is advertised as a monitoring feature. But it seems to be also a workaround for an ordering issue when starting primary and secondary processes concurrently, right?