> Hi Ian, Kevin, > dpdk 18.11 was officially released. Can you please inform what are the plans > for merging these series into dpdk-latest and dpdk-hwol branches? > Once merged - I would appreciate having the representor patches reviewed > (after being rebased). >
Thanks for Raising this Ophir, I would think the steps would be as follows: 1. Merge latest changes from OVS master to dpdk-latest. (Ian) 2. Create 18.11 support patch based on dpdk-latest. (Kevin) 3. Apply DPDK 18.11 patch to to support 18.11 to dpdk-latest(Ian). I intended to merge master to dpdk-latest tomorrow, if people have signed off on Kevins patch then I can also apply that to dpdk-latest. As regards moving merging 18.11 support to master I think we need to discuss the logistics of this a little more. Discussing this with Kevin I didn’t see a clear path so we have a few options. We could generate a patch on the diff between master and dpdk-latest with 18.11 support. Upside is we move in one patch to 18.11. However this could be messy though in terms of bisecting issues in the future, it would also be nice to give proper credit to the authors for the work done on individual patches. Another choice is to break the move into 2 patches. Patch 1 could move to 18.08 on master first (squashed commits based on the DPDK 18.08 work you submitted), then patch 2 would follow up immediately with a move to 18.11 based on what Kevin has submitted. This would at least avoid 1 large patch, would be easier to bisect in the future also if any issues occur. The downside here is that the DPDK compilation will fail in travis for DPDK 18.08 due to the deprecated API for hotplug attach/detach. I'd like to avoid introducing warnings into the OVS build if possible. What are peoples thoughts? Ian _______________________________________________ dev mailing list [email protected] https://mail.openvswitch.org/mailman/listinfo/ovs-dev
