Sorry for jumping in late in the review cycle. But I am not sure if there is significant advantage in store dpdk options in OVSDB.
On Fri, Jan 29, 2016 at 9:56 AM, Aaron Conole <acon...@redhat.com> wrote: > Currently, configuration of DPDK parameters is done via the command line > through a --dpdk **OPTIONS** -- command line argument. This has a number of > challenges, including: > * It must be the first option passed to ovs-vswitchd > This can be improved by specifying dpdk options in quotes, as --dpdk "options", then --dpdk can be any where in the command line. > * It breaks from the way most other things are configured in OVS > ovs-vswitchd still has command line options. > * It doesn't allow an easy way to populate defaults > why not? Is there an example? One draw back of storing command line options in OVSDB is that ovs-vswitchd needs to connect to OVSDB first to learn about those options. In case we still want ovs-vswitch to drop user privilege, it will be good to only connect to OVSDB server as a regular user. The other draw back is to handle version difference -- ovs-vswitchd and dpdk version can change over time, but ovsdb content *should* be compatible across versions. Storing too much configuration parameters make ovsdb become more version dependent. _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
