From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Burakov, Anatoly" Subject: Re: [PATCH v4 2/5] eal: use file to check if secondary process is ready Date: Tue, 6 Mar 2018 11:03:18 +0000 Message-ID: <427df582-b695-c894-f861-0461116d6150@intel.com> References: <06149b2941712f7abe5c02602d444b5a6937ea2f.1520000413.git.anatoly.burakov@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Cc: Bruce Richardson , jianfeng.tan@intel.com, keith.wiles@intel.com To: dev@dpdk.org Return-path: Received: from mga04.intel.com (mga04.intel.com [192.55.52.120]) by dpdk.org (Postfix) with ESMTP id 4C4475B1C for ; Tue, 6 Mar 2018 12:03:21 +0100 (CET) In-Reply-To: <06149b2941712f7abe5c02602d444b5a6937ea2f.1520000413.git.anatoly.burakov@intel.com> Content-Language: en-US List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org Sender: "dev" On 02-Mar-18 3:14 PM, Anatoly Burakov wrote: > Previously, IPC would remove sockets it considers to be "inactive" > based on whether they have responded. We also need to prevent > sending messages to processes that are active, but haven't yet > finished initialization. > > This will create a "init file" per socket which will be removed > after initialization is complete, to prevent primary process from > sending messages to a process that hasn't finished its > initialization. > > Signed-off-by: Anatoly Burakov > --- Self-NACK on this patch. Secondary processes may initialize data structures, which means IPC has to be active during init. Each subsystem will therefore have to synchronize access to IPC on their own. (For example, memory hotplug will only block IPC for a short period between rte_config_init() and init of memory/heap init) -- Thanks, Anatoly