Hello Keith/Anatoly,
Another strange thing, it appears that if i keep a
breakpoint (using gdb) on my async intr handler(bnxt_int_handler), then it
seems to hit it (after the alarm callback is invoked first) and then i can
see both this alarm going off every 2s and those async/interrupts arriving
on my driver....
Thanks
Som
On Sat, Nov 3, 2018 at 9:58 AM Somnath Kotur <somnath.ko...@broadcom.com>
wrote:
> Hi Anatoly/keith,
> I just tried using rte_eal_alarm_set() in the driver
> like so:
>
> rte_eal_alarm_set(US_PER_S * 2, timer0_cb, (void *)data);
>
> The moment i start this off, i stop getting async events/interrupt
> notifications in my driver ...I'm hitting the same problem as it was before
> with rte_timer_manage() as well.
> What is going wrong here ? Something we are missing ?
>
> Thanks
> Som
>
> On Sat, Nov 3, 2018 at 8:06 AM Somnath Kotur <somnath.ko...@broadcom.com>
> wrote:
>
>> Thank you Anatoly and keith for your replies. What i still don't get is
>> why the two cannot seem to co-exist?
>> That is , whenever this while loop was running in the EAL thread that i
>> showed in the code, my driver would stop receiving interrupts/async events
>> ...Do we understand that?
>> But you are right Anatoly, i need something to be called in my driver at
>> a cadence of ~2s, I was registering timers in my driver and running
>> rte_timer_manage() in this seperate thread to check and ensure the
>> callbacks are executed on expiry.
>> so if you are saying, i can achieve same functionality using rte_alarm()
>> while i can get async events in my driver at the same time, i will explore
>> this option
>> Thanks a lot
>>
>> Som
>>
>> On Fri, Nov 2, 2018 at 8:07 PM Wiles, Keith <keith.wi...@intel.com>
>> wrote:
>>
>>>
>>>
>>> > On Nov 2, 2018, at 9:35 AM, Wiles, Keith <keith.wi...@intel.com>
>>> wrote:
>>> >
>>> >
>>> Sorry, meant to hit cancel for my previous email, Anatoly answered it
>>> correctly.
>>>
>>> Regards,
>>> Keith
>>>
>>>
