2015-06-05 16:07, Andrew Harvey: > On 6/5/15, 3:46 AM, "Thomas Monjalon" <thomas.monjalon at 6wind.com> wrote: > >Stephen and me say the same thing about using the ethdev API. > > And your would have a point would be valid if dpdk were available to every > interface we support (it is not) and on every processor architecture that > we support (it is not) and every OS we support (it is not). So to > minimize entropy in the code why not leave the client code the same > ioctl(fd, ?) and hide the implementation > detail in a wrapper library.
Please, explain the relation between an ioctl and the DPDK.
