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

2018-03-12 Thread Jerin Jacob
-Original Message- > Date: Mon, 12 Mar 2018 14:30:49 + > From: "Eads, Gage" > To: Jerin Jacob > CC: "dev@dpdk.org" , "Van Haaren, Harry" > , "hemant.agra...@nxp.com" > , "Richardson, Bruce" > , "santosh.shu...@caviumnetworks.com" > , "nipun.gu...@nxp.com" > > Subject: RE: [PATCH

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

2018-03-12 Thread Eads, Gage
> -Original Message- > From: Jerin Jacob [mailto:jerin.ja...@caviumnetworks.com] > Sent: Monday, March 12, 2018 1:25 AM > To: Eads, Gage > Cc: dev@dpdk.org; Van Haaren, Harry ; > hemant.agra...@nxp.com; Richardson, Bruce ; > santosh.shu...@caviumnetworks.com; nipun.gu...@nxp.com > Subjec

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

2018-03-11 Thread Jerin Jacob
-Original Message- > When an event device is stopped, it drains all event queues. 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

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

2018-03-08 Thread Gage Eads
When an event device is stopped, it drains all event queues. 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 registere