05/12/2017 20:26, Neil Horman: > I get that much of dpdk relies on the fact that the application either handles > all the locking, or architects itself so that a single thread of execution (or > at least only one thread at a time), is responsible for packet processing and > port configuration.
Yes, for now, configuration is synchronized at application level. It is a constraint for applications. It may be an issue for multi-process applications, or for libraries aiming some device management. The first obvious bug to fix is race in device allocation. It will become more real with hotplug support.
