[dpdk-dev] [PATCH v4 1/2] eventdev: add device stop flush callback

Jerin Jacob jerin.jacob at caviumnetworks.com
Thu Mar 29 20:34:14 CEST 2018


-----Original Message-----
> Date: Thu, 29 Mar 2018 11:02:55 +0000
> From: "Van Haaren, Harry" <harry.van.haaren at intel.com>
> To: "jerin.jacob at caviumnetworks.com" <jerin.jacob at caviumnetworks.com>,
>  "hemant.agrawal at nxp.com" <hemant.agrawal at nxp.com>, "Ma, Liang J"
>  <liang.j.ma at intel.com>
> CC: "Eads, Gage" <gage.eads at intel.com>, "Richardson, Bruce"
>  <bruce.richardson at intel.com>, "santosh.shukla at caviumnetworks.com"
>  <santosh.shukla at caviumnetworks.com>, "nipun.gupta at nxp.com"
>  <nipun.gupta at nxp.com>, "dev at dpdk.org" <dev at dpdk.org>
> Subject: RE: [dpdk-dev] [PATCH v4 1/2] eventdev: add device stop flush
>  callback
> 
> (+Liang Ma for OPDL maintainer)
> 
> Ping to maintainers, is the below suggestion acceptable for your PMDs?
> 
> Summary of suggestion:
> - After event_dev_stop() dequeue() is no longer allowed on any thread
> - All events in the system (queues, ports, intermediary buffers) will be passed to a user-supplied callback for cleaning up events.

+1. That's works for octeontx eventdev PMD.



More information about the dev mailing list