From: Thomas Monjalon <thomas.monjalon@6wind.com>
To: "Zhang, Helin" <helin.zhang@intel.com>,
Stephen Hemminger <stephen@networkplumber.org>
Cc: dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK and HW offloads
Date: Sun, 20 Mar 2016 20:18:57 +0100 [thread overview]
Message-ID: <29795767.yLuRT7a5hO@xps13> (raw)
In-Reply-To: <F35DEAC7BCE34641BA9FAC6BCA4A12E70A9CD70B@SHSMSX104.ccr.corp.intel.com>
2016-03-20 14:17, Zhang, Helin:
> From: Thomas Monjalon [mailto:thomas.monjalon@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 bothers me enough that I would recommend removing much of the
> > filter/offload/ptype stuff from DPDK!
> >
> > One of the biggest challenge is to think about a good filtering API.
> > The offloading has some interaction with the mbuf struct.
> >
> > I would like to suggest rewriting ethdev API by keeping it as is for some time for
> > compatibility while creating a new one. What about the prefix dpdk_netdev_ to
> > progressively replace rte_eth_dev?
>
> I totally agree with to add new and generic APIs for user applications. But I don't
> think we need to remove all current APIs. Generic APIs may not support all advanced
> hardware features, while specific APIs can. Why not support all? One generic APIs for
> common users, and others APIs for advanced users.
Yes we cannot access to every features of a device through generic API.
Until now we were trying to add an ethdev API for every features even if it
is used by only one driver.
I think we should allow a direct access to the driver by the applications and
work on generic API only for common features.
next prev parent reply other threads:[~2016-03-20 19:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-18 17:16 Stephen Hemminger
2016-03-18 18:00 ` Thomas Monjalon
2016-03-20 14:17 ` Zhang, Helin
2016-03-20 19:18 ` Thomas Monjalon [this message]
2016-03-21 14:52 ` Bruce Richardson
2016-03-21 15:26 ` Kyle Larose
2016-03-22 5:50 ` Qiu, Michael
2016-03-22 10:19 ` Bruce Richardson
2016-03-22 12:19 ` Jay Rolette
2016-03-22 17:17 ` Stephen Hemminger
2016-03-22 17:41 ` Jerin Jacob
2016-03-23 2:47 ` Qiu, Michael
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=29795767.yLuRT7a5hO@xps13 \
--to=thomas.monjalon@6wind.com \
--cc=dev@dpdk.org \
--cc=helin.zhang@intel.com \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).