[ovs-dev] OVS DPDK Latest & HWOL Branches

Ben Pfaff blp at ovn.org
Tue Aug 14 21:19:10 UTC 2018


On Tue, Aug 14, 2018 at 04:42:06PM +0000, Stokes, Ian wrote:
> Recently at the OVS DPDK community meeting the case for 2 new branches was raised.
> 
> https://mail.openvswitch.org/pipermail/ovs-dev/2018-August/350898.html
> 
> These branches would be:
> 
> (i) OVS DPDK Latest: This branch would essentially be OVS master using the latest DPDK release (Including non LTS releases).
> 
> The purpose of this branch would be to allow OVS DPDK developers to assess the latest DPDK releases with OVS and provide feedback to the DPDK community if changes are required. Currently OVS transitions between supported DPDK releases using DPDK LTS releases only. DPDK LTS releases happen annually. The next DPDK LTS release would be 18.11. However the other non-lts DPDK releases (x.02, x.05, x.08) can introduce/change APIs that impact OVS DPDK (Such as the HWOL). This feedback would be in place for the next LTS release before OVS transitions to the next x.11 LTS.
> 
> (ii) OVS DPDK HWOL: This branch would be forked from OVS DPDK Latest but would encompass the HWOL development work that is ongoing.
> 
> The feeling as regards the need for a OVS DPDK HWOL branch is that it requires new features only available in the latest DPDK releases and that there will be a lot of code rework required as its validated with various HW devices over time before an acceptable solution will be in place.
> 
> There was a question as regards the logistics of where the branches should reside. It was suggested that they could be part of the OVS Repo to centralize the development work but that is obviously something that would have to be raised with yourself and the other project maintainers.
> 
> An alternative would be that it would be hosted on a developers GitHub repo similar to how the dpdk_merge branches currently work.
> 
> Neither of the branches would be subject to releases as the end goal of the development work carried out on them would make its way into OVS Master eventually.

This seems reasonable, as long as it doesn't overburden developers with
branches.

How do you prefer to host it?  Any of the following would be fine with
me, in descending order of preference:

* Host in openvswitch github repo forked from main openvswitch/ovs repo.

* Host in developer github repo.

* Host in main openvswitch/ovs repo as separate branches.

Thanks,

Ben.


More information about the dev mailing list