Thread (33 messages) 33 messages, 4 authors, 2017-12-01

Re: [RFC PATCH 0/1] eventtimer: introduce event timer wheel

From: Thomas Monjalon <hidden>
Date: 2017-08-29 15:49:00

29/08/2017 17:41, Jerin Jacob:
From: Thomas Monjalon <redacted>
quoted
25/08/2017 12:25, Jerin Jacob:
quoted
From: "Carrillo, Erik G" <redacted>
[...]
quoted
quoted
In summary, it looks like our solutions align fairly well, and I propose that we take on the software implementation if there are no objections.
Sure, no objection.
Good to see such a basic function generalized for NPU and CPU.

Are you going to use rte_timer for CPU implementation?
Does it mean that event_timer supersedes rte_timer?
IMO, we don't need to supersedes the rte_timer. The eventdev or event_timer is
an optional component. It is application decision to use poll mode vs event
driver model or combination of two.
Trying to make clear when using poll mode or event model,
regarding CPU/NPU differences:
If using poll mode + rte_timer, we cannot leverage NPU offloads.
If using event model, is it as much efficient for generic CPU?
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help