On 12/03/2015 06:23 AM, Aaron Conole wrote:
Existing DPDK integration is provided by use of command line options which
must be split out and passed to librte in a special manner. However, this
forces any configuration to be passed by way of a special DPDK flag, and
interferes with ovs+dpdk packaging solutions.
This commit delays dpdk initialization until after the OVS database connection
is established, and then initializes librte. It pulls all of the config data
from the OVS database, and assembles a new argv/argc pair to be passed along.
There needs to be a way to turn off DPDK even when support for it is
built in since it requires extra setup and failing to initialize will
tear down the whole ovs-vswitchd process. So in fact it probably should
default to off.
It'd be nice to have something smarter than a big "DPDK on/off" switch
in the db, such as lazy initialization only when needed (ie dpdk ports
are added) but there are quite a few problems with that I suspect.
- Panu -
_______________________________________________
dev mailing list
dev@openvswitch.org
http://openvswitch.org/mailman/listinfo/dev
