On Fri, Mar 31, 2017 at 02:43:15PM +0200, Thomas Monjalon wrote:
> 2017-03-30 19:06, Jerin Jacob:
> > 2) ethdev integration is pending.
>
> What is pending exactly?
As a standalone library, Nothing is pending in eventdev.
There are some HW features in the NIC side in some Hardwares that helps
in
2017-03-30 19:06, Jerin Jacob:
> 2) ethdev integration is pending.
What is pending exactly?
[...]
> Based on the above status, I would like to merge eventdev to DPDK
> v17.05 with EXPERIMENTAL tag and address pending work in v17.08 and
> remove the EXPERIMENTAL tag.
>
> Thomas and all,
>
> Thou
> From: Jerin Jacob [mailto:jerin.ja...@caviumnetworks.com]
> Sent: Thursday, March 30, 2017 2:37 PM
> To: Van Haaren, Harry
> Cc: dev@dpdk.org; thomas.monja...@6wind.com; hemant.agra...@nxp.com;
> Richardson, Bruce
>
> Subject: Re: [dpdk-dev] [PATCH] doc: add eventdev l
On Wed, Mar 15, 2017 at 05:21:18PM +, Harry van Haaren wrote:
> This commit adds an entry in the programmers guide
> explaining the eventdev library.
>
> The rte_event struct, queues and ports are explained.
> An API walktrough of a simple two stage atomic pipeline
> provides the reader with a
> From: dev [mailto:dev-boun...@dpdk.org] On Behalf Of Harry van Haaren
> Sent: Wednesday, March 15, 2017 5:21 PM
> To: dev@dpdk.org
> Cc: Van Haaren, Harry
> Subject: [dpdk-dev] [PATCH] doc: add eventdev library to programmers
> guide
>
> This commit adds an entry
This commit adds an entry in the programmers guide
explaining the eventdev library.
The rte_event struct, queues and ports are explained.
An API walktrough of a simple two stage atomic pipeline
provides the reader with a step by step overview of the
expected usage of the Eventdev API.
Signed-off-
6 matches
Mail list logo
