On Mon, Aug 2, 2021 at 9:45 PM Mattias Rönnblom <mattias.ronnb...@ericsson.com> wrote: > > Extend Eventdev API to allow for event devices which require various > forms of internal processing to happen, even when events are not > enqueued to or dequeued from a port. > > RFC v2: > - Change rte_event_maintain() return type to be consistent > with the documentation. > - Remove unused typedef from eventdev_pmd.h. > > Signed-off-by: Mattias Rönnblom <mattias.ronnb...@ericsson.com> > Tested-by: Richard Eklycke <richard.ekly...@ericsson.com> > Tested-by: Liron Himi <lir...@marvell.com> > --- > lib/eventdev/rte_eventdev.h | 62 +++++++++++++++++++++++++++++++++++++ > 1 file changed, 62 insertions(+) > > +/** > + * Maintain an event device. > + * > + * This function is only relevant for event devices which has the > + * RTE_EVENT_DEV_CAP_REQUIRES_MAINT flag set. Such devices requires > + * the application to call rte_event_maintain() on a port during periods > + * which it is neither enqueuing nor dequeuing events from this > + * port. No port may be left unattended. > + * > + * An event device's rte_event_maintain() is a low overhead function. In > + * situations when rte_event_maintain() must be called, the application > + * should do so often.
See rte_service_component_register() scheme, If a driver needs additional house keeping it can use DPDK's service core scheme to abstract different driver requirements.We may not need any public API for this.
