On Fri, Feb 09, 2024 at 02:44:04PM +0530, Jerin Jacob wrote: > On Fri, Feb 2, 2024 at 6:11 PM Bruce Richardson > <bruce.richard...@intel.com> wrote: > > > > Clarify the meaning of the NEW, FORWARD and RELEASE event types. > > For the fields in "rte_event" struct, enhance the comments on each to > > clarify the field's use, and whether it is preserved between enqueue and > > dequeue, and it's role, if any, in scheduling. > > > > Signed-off-by: Bruce Richardson <bruce.richard...@intel.com> > > --- > > V3: updates following review > > --- > > lib/eventdev/rte_eventdev.h | 161 +++++++++++++++++++++++++----------- > > 1 file changed, 111 insertions(+), 50 deletions(-) > > > > diff --git a/lib/eventdev/rte_eventdev.h b/lib/eventdev/rte_eventdev.h
<snip> > > + * the scheduler is now allowed to schedule events from that flow from to > > another port. > > + * However, the atomic locks may be still held until the next > > rte_event_dequeue_burst() > > + * call; enqueuing an event with opt type @ref RTE_EVENT_OP_RELEASE allows, > > Is ";" intended? Yes, it was. :-) /Bruce
