2016-03-08 09:58, Van Haaren, Harry: > From: David Marchand [mailto:david.marchand at 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?
