-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 Hi Daniele
Apologies for the lag - I've been away/offline for a few weeks. On 12/08/15 22:34, Daniele Di Proietto wrote: > There has been some discussion lately about the status of the Open > vSwitch port to DPDK. While part of the code has been tested for > quite some time, I think we can agree that there are a few rough > spots that prevent it from being easily deployed and used. [...] > - Interface management and naming: interfaces must be manually > removed from the kernel drivers. > > We still don't have an easy way to identify them. Ideas are > welcome: how can we make this user friendly? Is there a better > solution on the DPDK side? > > How are DPDK interfaces handled by linux distributions? I've heard > about ongoing work for RHEL and Ubuntu, it would be interesting to > coordinate. For Ubuntu wily (currently in development) we've been aiming to have initial packages for DPDK 2.0.0 - this is still work in progress, and does have some rough edges so may not make the cut for release, but we'll see how it goes. In terms of interface management, we've come up with a solution that allows administrators to configure DPDK managed interfaces via a configuration file - /etc/dpdk/interfaces. This takes the format: <bus> <id> <driver> See [0] for full details. An associated startup script reads this file and reloads drivers as required so that the configured interfaces can be used by DPDK/OVS. The same init script also deals with configuring hugepages, configuration of which is read from /etc/dpdk/dpdk.conf. See [1] for full details. > - Packaging: how should the distributions package DPDK and OVS? > Should there only be a single build to handle both the kernel and > the userspace datapath, eventually dynamically linked to DPDK? Due to the CPU compile time requirements for DPDK, we intend to take the approach of providing a vanilla ovs-vswitchd binary that is not DPDK enabled, with an alternative which can be switched in that does support DPDK - see [3] for more details on how this would work. I'm currently assuming the only binary we need to enable/provide for DPDK support is ovs-vswitchd - please correct that assumption if its not true! Until DPDK supports runtime cpu feature detection (which other members of my team have been discussing with the DPDK project), we can't really support in single binary in Ubuntu. [0] https://git.launchpad.net/~ubuntu-server/dpdk/tree/debian/dpdk.interface s?h=ubuntu-wily [1] https://git.launchpad.net/~ubuntu-server/dpdk/tree/debian/dpdk.conf?h=ub untu-wily [2] http://bazaar.launchpad.net/~james-page/ubuntu/wily/openvswitch/2.4.0/vi ew/head:/debian/openvswitch-switch.README.Debian#L207 - -- James Page Ubuntu and Debian Developer james.p...@ubuntu.com jamesp...@debian.org -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJV5Yk/AAoJEL/srsug59jD6vIP/Ai9g2wNrkoZ8t/cDzi2aiBa k/GFfwQYYeDHyAGyzL3h0OIRQ95/ZyvYjFa9JyQEE+KY/NzoV9I0jQZEOBMSOu7q uoMlF9Qdtkx+NNZ6gXgrZhJKG5NQuGK33ICH1rR+p9zf9+ILvGa2kc5LWhZzXc7s 8DTrG48NHEpPNFCrh7GTHy5/QtxDnomiN9OmopgstPt46RdbfDXnA0hjLEP/fRT2 uontOhq7CPp9QzjhvZE1PWipSxUOi3FlswNTogumwrLzBw6YPmlCws4ar4MYWyaQ fCEnMDC00qZWb55v/f/9WMygNwCdbGuHqvb3jo9kBdYkdWFy+sNqv5o3MiJC3hMr Jl2rGYQ7In4j4yXsgL7LDetdk2NFZD7fsoLFQmdHjbq6GCTvNQwIbDOmffRqe6Xg 4zeTboceX4qNrqnZUY4HXaM6viaZas87mMKF+YWP5vsi7ob9Uom1uoprMuCTkwJZ F8p2synJ92kPjHsudNKtUb46n0ZH8KrAs+CPrR2PSU6+4xPq9FsD8NXLCBgs4SaM 6iZVRO/6TC53cuAAk1x5Vd9Q9jjNlq5hCdF8aljKbPaxg53NtZnbAcK082CislL9 Yvg1BUHz1Bbas0cYbLR/wp3YExYtZlA1FcbxOdzoFq/A4mL1YqBjf1HmUkmz3SFa 6Z0rNZkErtPTPPr3dua0 =jCp1 -----END PGP SIGNATURE----- _______________________________________________ dev mailing list dev@openvswitch.org http://openvswitch.org/mailman/listinfo/dev
