On 10/5/2016 6:47 PM, jt at labs.hpe.com (Jean Tourrilhes) wrote: > If the primary and secondary process were build using different build > systems, the list of constructors included by the linker in each > binary might be different. Tailqs are registered via constructors, so > the linker magic will directly impact which tailqs are registered with > the primary and the secondary. > > DPDK currently assumes that the secondary has a subset of the tailqs > registered at the primary. In some build scenario, the secondary might > register a tailq that the primary did not register. In this case, > instead of exiting with a panic, just unregister the offending tailq > and allow the secondary to run. > > Signed-off-by: Jean Tourrilhes <jt at labs.hpe.com>
A lot changed in multiprocess support in last two years, updating status of this patch as 'Rejected', if the issue is still valid can you please either send a new version or report the issue in bugzilla? Thanks, ferruh
