[ovs-dev] [PATCH v5 0/4] Convert DPDK configuration from command line to DB based
Aaron Conole
aconole at redhat.com
Mon Jan 18 20:28:30 UTC 2016
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
* It breaks from the way most other things are configured in OVS
* It doesn't allow an easy way to populate defaults
This series brings the following changes to openvswitch:
* All DPDK options are taken from the ovs database rather than the
command line
* DPDK lcores are optionally auto-assigned to a single core based on the
bridge coremask.
* Updated documentation
v2:
* Dropped the vhost-user socket configuration options. Those can be re-added
as an extension
* Incorporated feedback from Kevin Traynor.
v3:
* Went back to a global dpdk-init
* Language cleanup and various minor fixes
v4:
* Added a way to pass arbitrary eal arguments
v5:
* Restore the socket-mem default, and fix up the ovs-dev.py script, along
with the manpage for ovsdb-server
Aaron Conole (4):
netdev-dpdk: Restore thread affinity after DPDK init
netdev-dpdk: Convert initialization from cmdline to db
netdev-dpdk: Autofill lcore coremask if absent
netdev-dpdk: Allow arbitrary eal arguments
FAQ.md | 6 +-
INSTALL.DPDK.md | 86 ++++++++++++----
lib/netdev-dpdk.c | 249 ++++++++++++++++++++++++++++++++++++---------
lib/netdev-dpdk.h | 22 ++--
utilities/ovs-dev.py | 7 +-
vswitchd/bridge.c | 3 +
vswitchd/ovs-vswitchd.8.in | 5 +-
vswitchd/ovs-vswitchd.c | 25 +----
vswitchd/vswitch.xml | 128 ++++++++++++++++++++++-
9 files changed, 426 insertions(+), 105 deletions(-)
--
2.5.0
More information about the dev
mailing list