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

[Jerin Jacob <jerin.jacob@caviumnetworks.com>]

-----Original Message-----
> Date: Tue, 3 Apr 2018 06:56:49 +0530
> From: Jerin Jacob <jerin.jacob@caviumnetworks.com>
> To: Gage Eads <gage.eads@intel.com>
> CC: dev@dpdk.org, harry.van.haaren@intel.com, hemant.agrawal@nxp.com,
>  bruce.richardson@intel.com, santosh.shukla@caviumnetworks.com,
>  nipun.gupta@nxp.com, liang.j.ma@intel.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 <gage.eads@intel.com>
> > To: dev@dpdk.org
> > CC: jerin.jacob@caviumnetworks.com, harry.van.haaren@intel.com,
> >  hemant.agrawal@nxp.com, bruce.richardson@intel.com,
> >  santosh.shukla@caviumnetworks.com, nipun.gupta@nxp.com,
> >  liang.j.ma@intel.com
> > Subject: [PATCH v5] eventdev: add device stop flush callback
> > X-Mailer: git-send-email 2.7.4
> > 
> > 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 registered by any process that may call rte_event_dev_stop().
> > 
> > This commit also clarifies the behavior of rte_event_dev_stop().
> > 
> > This follows this mailing list discussion:
> > http://dpdk.org/ml/archives/dev/2018-January/087484.html
> > 
> > Signed-off-by: Gage Eads <gage.eads@intel.com>
> 
> Acked-by: Jerin Jacob <jerin.jacob@caviumnetworks.com>

Applied to dpdk-next-eventdev/master. Thanks.