[dpdk-dev] Poor device abstraction's

ake that happen. Even semi-freezing anything prior to that would be premature. -Venky -Original Message- From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Neil Horman Sent: Friday, April 11, 2014 10:47 AM To: Stephen Hemminger Cc: dev at dpdk.org Subject: Re: [dpdk-dev] Poor device ab

[dpdk-dev] Poor device abstraction's

ngs that are unnecessecary? That might give us a good starting point to see what else is needed Neil > -Venky > > -Original Message- > From: dev [mailto:dev-bounces at dpdk.org] On Behalf Of Neil Horman > Sent: Friday, April 11, 2014 10:47 AM > To: Stephen Hemminger &

[dpdk-dev] Poor device abstraction's

On Fri, Apr 11, 2014 at 10:33:31AM -0700, Stephen Hemminger wrote: > One of my pet peeve's is that the device driver config does not abstract > the properties of the Ethernet device. The existing parameters match those > of Intel's Ethernet hardware but not much else. It also makes it hard > to wri

[dpdk-dev] Poor device abstraction's

One of my pet peeve's is that the device driver config does not abstract the properties of the Ethernet device. The existing parameters match those of Intel's Ethernet hardware but not much else. It also makes it hard to write generic applications. If the application has to query the device driver