2015-06-05 17:24, Andrew Harvey: > On 6/5/15, 5:47 AM, "Bruce Richardson" <bruce.richardson at intel.com> wrote: > >> From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > >> > That's why we need to understand what we (or you) are missing. > >> > Maybe that it would be clearer with some code examples (which would > >> > go in the lib documentation if any). > >> > > >> > Thanks > > > >How about doing this work as a sample application initially, to > >demonstrate how > >an application written using ethtool APIs could be shimmed to use DPDK > >underneath. > >The ethtool to dpdk mapping could be contained in a single header file > >(or header > >and c file) inside the sample app. This would allow easy re-use of the > >shim > >layer, while at the same time not making it part of the core DPDK > >libraries. > > > >Regards, > >/Bruce > > This would appear to be the most pragmatic way forward. It would allow > others to see more of the code and judge its value for themselves. I have > no issues with this approach if others agree.
Since the beginning of this thread, a doc is requested (many times) to show the benefit of integrating such a layer. If you prefer coding a full example, it would probably also be fine.
