Message ID | 20200701202359.17006-1-stephen@networkplumber.org (mailing list archive) |
---|---|
Headers | show |
Series | Replace references to master and slave | expand |
On 01-Jul-20 9:23 PM, Stephen Hemminger wrote: > This set of patches changes the API and conventions around referring > to DPDK lcores. The first patch changes rte_get_master_lcore_id > and related calls. The rest fix the DPDK to use the new naming. > > Buried in the documentation set are a couple of patches where > we were using incorrect naming around primary/secondary process. > > This will could/should be flagged as an API policy violation > since new API is jumping the queue of EXPERIMENTAL. But we can > vote on the exception. > > The one area left to be fixed is the bonding device. > > v4 > - fix checkpatch warnings > note: this patchset will cause some false positives > v3 > - modify vhost to replace slave with client > - modify memif to replace slave with client > - fix variable names s2m becomes i2w etc. > Hi Stephen, This patchset does not apply on the latest master. Please rebase and resend.
On 01-Jul-20 9:23 PM, Stephen Hemminger wrote: > This set of patches changes the API and conventions around referring > to DPDK lcores. The first patch changes rte_get_master_lcore_id > and related calls. The rest fix the DPDK to use the new naming. > > Buried in the documentation set are a couple of patches where > we were using incorrect naming around primary/secondary process. > > This will could/should be flagged as an API policy violation > since new API is jumping the queue of EXPERIMENTAL. But we can > vote on the exception. > > The one area left to be fixed is the bonding device. > I am not too sure about the "initial" core term, it doesn't strike me as immediately obvious as to what "initial" core does. Perhaps "main" lcore would be more descriptive?