Re: [lng-odp] [API-NEXT PATCHv1 1/2] validation: increase timer expiration wait time

2016-01-19 Thread Maxim Uvarov
On 01/19/2016 01:54, Ivan Khoronzhuk wrote: Maxim, in general, I had no look in this test, it was working for me and I was happy. At fast glance I have some comments. Hope you will find time to correct it. ok, some comments bellow. On 15.01.16 11:14, Maxim Uvarov wrote: Following

Re: [lng-odp] [API-NEXT PATCHv1 1/2] validation: increase timer expiration wait time

2016-01-19 Thread Maxim Uvarov
On 01/19/2016 13:23, Ivan Khoronzhuk wrote: On 19.01.16 11:59, Maxim Uvarov wrote: On 01/19/2016 01:54, Ivan Khoronzhuk wrote: Maxim, in general, I had no look in this test, it was working for me and I was happy. At fast glance I have some comments. Hope you will find time to correct it.

Re: [lng-odp] [API-NEXT PATCHv1 1/2] validation: increase timer expiration wait time

2016-01-19 Thread Ivan Khoronzhuk
On 19.01.16 13:27, Maxim Uvarov wrote: On 01/19/2016 13:23, Ivan Khoronzhuk wrote: On 19.01.16 11:59, Maxim Uvarov wrote: On 01/19/2016 01:54, Ivan Khoronzhuk wrote: Maxim, in general, I had no look in this test, it was working for me and I was happy. At fast glance I have some comments.

Re: [lng-odp] [API-NEXT PATCHv1 1/2] validation: increase timer expiration wait time

2016-01-18 Thread Ivan Khoronzhuk
Maxim, in general, I had no look in this test, it was working for me and I was happy. At fast glance I have some comments. Hope you will find time to correct it. On 15.01.16 11:14, Maxim Uvarov wrote: Following current test logic validation test should correctly wait for all scheduled timer

[lng-odp] [API-NEXT PATCHv1 1/2] validation: increase timer expiration wait time

2016-01-15 Thread Maxim Uvarov
Following current test logic validation test should correctly wait for all scheduled timer expirations. Setting that time to 1ms is not correct due to code above schedules timer to 1.1ms and context switch in linux takes 10ms. Problem that odp_timer_pool_destroy() does not disarm all trigered