I very much support the proposal to make configuration of "physical" DPDK ports more explicit and flexible. Both the ability to specify the port by its PCI address as well as the ability to choose arbitrary port names are highly welcome.
+1 for idea and implementation. Can we combine this proposal with the ability to automatically hot-plug PCI devices that were not yet bound to DPDK-compatible drivers (e.g. igb_uio, vfio_pci etc) at start of ovs-vswitchd? BR, Jan > -----Original Message----- > From: dev [mailto:dev-boun...@openvswitch.org] On Behalf Of Ciara Loftus > Sent: Tuesday, 14 June, 2016 16:08 > To: dev@openvswitch.org > Subject: [ovs-dev] [PATCH RFC 0/1] netdev-dpdk: Arbitrary 'dpdk' port > naming > > This RFC patch addresses the restrictions placed on dpdk port names. > > Currently dpdk ports must be named dpdkX where X is the dpdk port-id. > This patch removes this restriction and introduces the requirement to specify > the pci address of the device in the other_config db. eg. > > ovs-vsctl add-port br0 my-port -- set Interface my-port type=dpdk > options:dpdk-pci=0000:06:00.0 > > This patch is a work in progress and minimal testing has been performed, > although a basic setup switching between two dpdk ports has been verified > to work. > > I'd welcome feedback on both the idea and the approach. > > INSTALL.DPDK.md | 10 ++++---- > NEWS | 2 ++ > lib/netdev-dpdk.c | 71 > +++++++++++++++++++++++++++++++++++++++++++++---------- > 3 files changed, 66 insertions(+), 17 deletions(-) > > -- > 2.4.3 > > _______________________________________________ > dev mailing list > dev@openvswitch.org > http://openvswitch.org/mailman/listinfo/dev _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
