Re: [dpdk-dev] [PATCH v5] eventdev: add device stop flush callback

ntel.com > Subject: Re: [dpdk-dev] [PATCH v5] eventdev: add device stop flush callback > User-Agent: Mutt/1.9.4 (2018-02-28) > > -Original Message- > > Date: Mon, 2 Apr 2018 13:03:30 -0500 > > From: Gage Eads > > To: dev@dpdk.org > > CC: jeri

Re: [dpdk-dev] [PATCH v5] eventdev: add device stop flush callback

-Original Message- > Date: Mon, 2 Apr 2018 13:03:30 -0500 > From: Gage Eads > To: dev@dpdk.org > CC: jerin.ja...@caviumnetworks.com, harry.van.haa...@intel.com, > hemant.agra...@nxp.com, bruce.richard...@intel.com, > santosh.shu...@caviumnetworks.com, nipun.gu...@nxp.com, > liang.j...@i

[dpdk-dev] [PATCH v5] eventdev: add device stop flush callback

When an event device is stopped, it drains all event queues and ports. These events may contain pointers, so to prevent memory leaks eventdev now supports a user-provided flush callback that is called during the queue drain process. This callback is stored in process memory, so the callback must be