Re: [lng-odp] Regarding how ODP closes scheduled PKTIOs

I agree, Maxim, before closing all the queues, they must be flushed. However, there are a number of problems, as I understand, in the current implementation: a) As you say, one could flush queue by queue, which is tedious (and may have some side effects if they are scheduled?). Alternatively,

Re: [lng-odp] Regarding how ODP closes scheduled PKTIOs

Hi Bill, I'll try to be there. -- Oriol Arcas Software Engineer Starflow Networks On Tue, May 2, 2017 at 5:01 AM, Bill Fischofer wrote: > Oriol: I've added this and the TM issue you raised to the agenda for > Tuesday's ODP public call. Please join us if you're able

Re: [lng-odp] Regarding how ODP closes scheduled PKTIOs

Correct steps are: 1. odp_pktio_stop() 2. flush queues (or with call to odp_schedule() while there are packets, or odp_queue_dequeue()). 3. odp_pktio_close(). I.e. when you call close() all queues have to be empty. Maxim. On 2 May 2017 at 06:01, Bill Fischofer wrote:

Re: [lng-odp] Regarding how ODP closes scheduled PKTIOs

Oriol: I've added this and the TM issue you raised to the agenda for Tuesday's ODP public call. Please join us if you're able to discuss this further. Thanks. Regards, Bill On Mon, May 1, 2017 at 7:04 AM, Bill Fischofer wrote: > > > On Thu, Apr 27, 2017 at 10:34 AM,

Re: [lng-odp] Regarding how ODP closes scheduled PKTIOs

On Thu, Apr 27, 2017 at 10:34 AM, Oriol Arcas wrote: > Hello, > > I have some questions regarding how scheduled PKTIOs are closed. Please > correct me if I am wrong... > > In ODP 1.11 Monarch (I think 1.14 as well) scheduled PKTIOs cannot be > closed before they are

[lng-odp] Regarding how ODP closes scheduled PKTIOs

Hello, I have some questions regarding how scheduled PKTIOs are closed. Please correct me if I am wrong... In ODP 1.11 Monarch (I think 1.14 as well) scheduled PKTIOs cannot be closed before they are stopped and unscheduled. This is why there are the transitional states PKTIO_STATE_STOP_PENDING