[dpdk-dev] DPDK and HW offloads

2016-03-23 Thread Qiu, Michael
On 3/22/2016 6:20 PM, Richardson, Bruce wrote: > On Tue, Mar 22, 2016 at 05:50:28AM +, Qiu, Michael wrote: >> On 3/21/2016 11:27 PM, Kyle Larose wrote: >>> On Mon, Mar 21, 2016 at 10:52 AM, Bruce Richardson >>> wrote: On Sun, Mar 20, 2016 at 08:18:57PM +0100, Thomas Monjalon wrote: >

[dpdk-dev] DPDK and HW offloads

2016-03-23 Thread Jerin Jacob
On Tue, Mar 22, 2016 at 10:17:21AM -0700, Stephen Hemminger wrote: > On Tue, 22 Mar 2016 07:19:01 -0500 > Jay Rolette wrote: > > > On Tue, Mar 22, 2016 at 5:19 AM, Bruce Richardson < > > bruce.richardson at intel.com> wrote: > > > > > On Tue, Mar 22, 2016 at 05:50:28AM +, Qiu, Michael

[dpdk-dev] DPDK and HW offloads

2016-03-22 Thread Bruce Richardson
On Tue, Mar 22, 2016 at 05:50:28AM +, Qiu, Michael wrote: > On 3/21/2016 11:27 PM, Kyle Larose wrote: > > On Mon, Mar 21, 2016 at 10:52 AM, Bruce Richardson > > wrote: > >> On Sun, Mar 20, 2016 at 08:18:57PM +0100, Thomas Monjalon wrote: > >>> 2016-03-20 14:17, Zhang, Helin: > From:

[dpdk-dev] DPDK and HW offloads

2016-03-22 Thread Stephen Hemminger
On Tue, 22 Mar 2016 07:19:01 -0500 Jay Rolette wrote: > On Tue, Mar 22, 2016 at 5:19 AM, Bruce Richardson < > bruce.richardson at intel.com> wrote: > > > On Tue, Mar 22, 2016 at 05:50:28AM +, Qiu, Michael wrote: > > > > > > Why not to implement one simple API with variable arguments, just

[dpdk-dev] DPDK and HW offloads

2016-03-22 Thread Jay Rolette
On Tue, Mar 22, 2016 at 5:19 AM, Bruce Richardson < bruce.richardson at intel.com> wrote: > On Tue, Mar 22, 2016 at 05:50:28AM +, Qiu, Michael wrote: > > > > Why not to implement one simple API with variable arguments, just like > > syscall ioctl() does. And drivers implement it's specific

[dpdk-dev] DPDK and HW offloads

2016-03-21 Thread Bruce Richardson
On Sun, Mar 20, 2016 at 08:18:57PM +0100, Thomas Monjalon wrote: > 2016-03-20 14:17, Zhang, Helin: > > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > > > 2016-03-18 10:16, Stephen Hemminger: > > > > Right now, all those offload features are pretty much unusable in a > > > > real

[dpdk-dev] DPDK and HW offloads

2016-03-21 Thread Kyle Larose
On Mon, Mar 21, 2016 at 10:52 AM, Bruce Richardson wrote: > On Sun, Mar 20, 2016 at 08:18:57PM +0100, Thomas Monjalon wrote: >> 2016-03-20 14:17, Zhang, Helin: >> > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] >> > > 2016-03-18 10:16, Stephen Hemminger: >> > > > Right now, all

[dpdk-dev] DPDK and HW offloads

2016-03-20 Thread Thomas Monjalon
2016-03-20 14:17, Zhang, Helin: > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > > 2016-03-18 10:16, Stephen Hemminger: > > > Right now, all those offload features are pretty much unusable in a > > > real product without lots and lots of extra codes and huge bug > > > surface. It

[dpdk-dev] DPDK and HW offloads

2016-03-20 Thread Zhang, Helin
> -Original Message- > From: Thomas Monjalon [mailto:thomas.monjalon at 6wind.com] > Sent: Saturday, March 19, 2016 2:01 AM > To: Stephen Hemminger > Cc: Zhang, Helin ; dev at dpdk.org > Subject: Re: DPDK and HW offloads > > 2016-03-18 10:16, Stephen Hemminger: > > As I look at how the

[dpdk-dev] DPDK and HW offloads

2016-03-18 Thread Thomas Monjalon
2016-03-18 10:16, Stephen Hemminger: > As I look at how the ethernet device interface in DPDK has exploded in > complexity; Yes I would like to start addressing this complexity in 16.07. > it makes life very hard for end users. The goal has been to enable all the > cool hardware > features,

[dpdk-dev] DPDK and HW offloads

2016-03-18 Thread Stephen Hemminger
As I look at how the ethernet device interface in DPDK has exploded in complexity; it makes life very hard for end users. The goal has been to enable all the cool hardware features, but it has put blinders on the driver devlopers; they are ignoring the fact that real applications can't just