On Fri, Oct 07, 2016 at 10:40:03AM +, Hemant Agrawal wrote:
> Hi Jerin/Narender,
Hi Hemant,
Thanks for the review.
>
> Thanks for the proposal and discussions.
>
> I agree with many of the comment made by Narender. Here are some
> additional comments.
>
> 1. rte_event_sche
Hi Jerin/Narender,
Thanks for the proposal and discussions.
I agree with many of the comment made by Narender. Here are some
additional comments.
1. rte_event_schedule - should support option for bulk dequeue. The size of
bulk should be a property of device, how much depth it
On Tue, Oct 04, 2016 at 09:49:52PM +, Vangati, Narender wrote:
> Hi Jerin,
Hi Narender,
Thanks for the comments.I agree with proposed changes; I will address these
comments in v2.
/Jerin
>
>
>
> Here are some comments on the libeventdev RFC.
>
> These are collated thoughts after discu
Hi Jerin,
Here are some comments on the libeventdev RFC.
These are collated thoughts after discussions with you & others to understand
the concepts and rationale for the current proposal.
1. Concept of flow queues. This is better abstracted as flow ids and not as
flow queues which implies
On Tue, Aug 09, 2016 at 09:48:46AM +0100, Bruce Richardson wrote:
> On Tue, Aug 09, 2016 at 06:31:41AM +0530, Jerin Jacob wrote:
> > Find below the URL for the complete API specification.
> >
> > https://rawgit.com/jerinjacobk/libeventdev/master/rte_eventdev.h
> >
> > I have created a supportive
On Tue, Aug 09, 2016 at 06:31:41AM +0530, Jerin Jacob wrote:
> Hi All,
>
> Find below an RFC API specification which attempts to
> define the standard application programming interface
> for event driven programming in DPDK and to abstract HW based event devices.
>
> These devices can support eve
Hi All,
Find below an RFC API specification which attempts to
define the standard application programming interface
for event driven programming in DPDK and to abstract HW based event devices.
These devices can support event scheduling and flow ordering
in HW and typically found in NW SoCs as an
7 matches
Mail list logo
