[dpdk-dev] Best Practices for PMD Verification before Upstream Requests
remy.horton at intel.com
Fri Nov 4 06:41:06 CET 2016
On 02/11/2016 20:21, Shepard Siegel wrote:
> Almost a year into our DPDK development, we have shipped an alpha version
> of our "Arkville" product. We've thankful for all the support from this
> Most everyone has suggested "get your code upstream ASAP"; but our
> team is cut from the "if it isn't tested, it doesn't work" cloth. We now
> have some solid miles on our Arkville PMD driver "ark" with 16.07. Mostly
> testpmd and a suite of user apps; dts not so much, only because our use
> case is a little different.
To me that sounds good enough for a v1 patch.
> One question that
> came up is "Should we do a thorough port and regression against 16.11 as a
> precursor to up streaming at 17.02?". Constructive feedback always welcome!
It is helpful, although bear in mind there is only so much you'll be
able to test. Patches sent to the mailing list are picked up by
patchwork for automated testing, so you'll find out quite quickly if
you've broken something.
And avoid top-posting.. :)
More information about the dev