From mboxrd@z Thu Jan 1 00:00:00 1970 From: David Marchand Subject: Re: [PATCH v6] eal: add function to check if primary proc alive Date: Tue, 8 Mar 2016 12:19:56 +0100 Message-ID: References: <1457350669-32582-1-git-send-email-harry.van.haaren@intel.com> <2251445.Z6GIcehbaX@xps13> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Cc: "dev@dpdk.org" To: Thomas Monjalon Return-path: Received: from mail-oi0-f41.google.com (mail-oi0-f41.google.com [209.85.218.41]) by dpdk.org (Postfix) with ESMTP id 5A4DE2C6B for ; Tue, 8 Mar 2016 12:20:16 +0100 (CET) Received: by mail-oi0-f41.google.com with SMTP id d205so8087934oia.0 for ; Tue, 08 Mar 2016 03:20:16 -0800 (PST) In-Reply-To: <2251445.Z6GIcehbaX@xps13> 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" On Tue, Mar 8, 2016 at 12:13 PM, Thomas Monjalon wrote: > 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? +1 -- David Marchand