Hey Thomas, Thanks for taking a look. My intentions is to port some of the new features on top of this patch (flow steering, ESP RSS – preparing the patches right now) which we are using inhouse to DPDK, however for that I require to upgrade definitions. The ownership of this definitions is VMware’s ESX team, my main goal was to keep the definitions identical to most recent ESX’s, for correctness and ease of maintenance later on, instead of just adding bits and pieces.
Does that sound good or should I follow a different approach? Thanks for the help, Edu PS. I mistakenly pushed this with private email address, I’ll change to vmware’s domain one next iteration. From: Thomas Monjalon Sent: Thursday, April 4, 2019 2:26 PM To: Eduard Serra Cc: dev@dpdk.org; eduse...@gmail.com; yongw...@vmware.com Subject: Re: [dpdk-dev] [PATCH] net/vmxnet3: synchronize vmxnet definitionswith 6.7 public Hi, > From: Eduard Serra <ese...@vmware.com> > > Synchronize new definitions made public defs on ESX 6.7, which > include support for variety of new features and fixes on vmxnet3 > driver. Please, would it be possible to split this patch, and add explanations in each patch for each feature or cleanup? Thank you
