From mboxrd@z Thu Jan 1 00:00:00 1970 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) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=6wind-com.20150623.gappssmtp.com; s=20150623; h=from:to:cc:subject:date:message-id:organization:user-agent :in-reply-to:references:mime-version:content-transfer-encoding; bh=hgdkt5RLWe1//un6NiJNL84UYhyrmL94sdFIjle8yNU=; b=hNxfOX/kgohmE4NA73L8V6awVMoXvKKREfAFN8G6i42+rFl508qEMRdwczwI7lR9s0 PQibOPBZkEgEGUaBwc+8/L7UMpuwGrOuOz5BFGoxm2BszJaLFv+tonbs2Y2i246idMH6 17ESvIcvgtDzjAjs1XECToppPdDhYGalRtSwjQ7AX6GS2O/Vb17ZIuqSenbbNIiHJk8J SAIHEwFdYbJ7PThubR7qTpxMl+N0wa3L8zFe8O1K3qk89tkv09NxL3bU1WPdcqZ5ERch Q3cTtpNoBMc6Z6KIdyrBg3wF63SfeaZGkJ70dYZMHL8EVZmSI4xS7wIclEGtQExVYUF4 4jfw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:to:cc:subject:date:message-id:organization :user-agent:in-reply-to:references:mime-version :content-transfer-encoding; bh=hgdkt5RLWe1//un6NiJNL84UYhyrmL94sdFIjle8yNU=; b=isiTlcaVoPGX0voQxpbsDLuf0BNl9/DlKkV3r8opnIpmucOjaGTrisCPndAQsIbWnY wcXKUWI+NqrtAT3/EpW4yfZoablmKumF+DhLTccqxDqsYdXWu7HXVWabCzXa88RuoQWt CARza3zhNBv0RJUQg61fIZ1sz/TtDlLdJhA0aXnUXKoNOqm2UIXm1p0h/XbgGpUtYjLi njLAsXl0qDxlWgBZIfiwYK8IxO0BmJOT4jjRZEpBDEzsuew+9NW2GL1YifxNSFnxHc9J u4Ybc5uh2USXgauPzaIiSl3yRQBxadNj4/70ma7mv9HG74JZaMqnSv3Ba7jS4OhpLYqz GdPA== X-Gm-Message-State: AD7BkJKxIUhHvtEFHiDwWAu9PyLjrbZfp4d0MjvrxfUG9i1gEcEhC4HRW5WcqODBrDFci1Z5 X-Received: by 10.194.242.202 with SMTP id ws10mr28247432wjc.3.1457435728644; Tue, 08 Mar 2016 03:15:28 -0800 (PST) Received: from xps13.localnet (171.36.101.84.rev.sfr.net. [84.101.36.171]) by smtp.gmail.com with ESMTPSA id u202sm18396094wmd.24.2016.03.08.03.15.27 (version=TLSv1/SSLv3 cipher=OTHER); Tue, 08 Mar 2016 03:15:27 -0800 (PST) From: Thomas Monjalon To: "Van Haaren, Harry" Date: Tue, 08 Mar 2016 12:13:50 +0100 Message-ID: <2251445.Z6GIcehbaX@xps13> Organization: 6WIND User-Agent: KMail/4.14.10 (Linux/4.1.6-1-ARCH; KDE/4.14.11; x86_64; ; ) In-Reply-To: References: <1457350669-32582-1-git-send-email-harry.van.haaren@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Cc: dev@dpdk.org Subject: Re: [dpdk-dev] [PATCH v6] 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, 08 Mar 2016 11:15:28 -0000 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?