[dpdk-dev] [PATCH v4 2/5] eal: use file to check if secondary process is ready
Burakov, Anatoly
anatoly.burakov at intel.com
Tue Mar 6 12:03:18 CET 2018
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 <anatoly.burakov at intel.com>
> ---
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
More information about the dev
mailing list