From: Somnath Kotur <somnath.kotur@broadcom.com>
To: keith.wiles@intel.com
Cc: anatoly.burakov@intel.com, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] Question about rte_manage_timer() and eal_intr_handle_interrupts
Date: Sat, 3 Nov 2018 12:49:40 +0530 [thread overview]
Message-ID: <CAOBf=mst5i=OD=eaaFv+g96w5tmLHfGf5WQizj1C5ux_DEmwZA@mail.gmail.com> (raw)
In-Reply-To: <CAOBf=msoVksZToBROnLFoE-VRmc2G0Vu2cYQ7MNmdTg9n_UFzw@mail.gmail.com>
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.kotur@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.kotur@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.wiles@intel.com>
>> wrote:
>>
>>>
>>>
>>> > On Nov 2, 2018, at 9:35 AM, Wiles, Keith <keith.wiles@intel.com>
>>> wrote:
>>> >
>>> >
>>> Sorry, meant to hit cancel for my previous email, Anatoly answered it
>>> correctly.
>>>
>>> Regards,
>>> Keith
>>>
>>>
prev parent reply other threads:[~2018-11-03 7:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-02 4:00 Somnath Kotur
2018-11-02 6:08 ` Somnath Kotur
2018-11-02 11:31 ` Burakov, Anatoly
2018-11-02 14:35 ` Wiles, Keith
2018-11-02 14:37 ` Wiles, Keith
2018-11-03 2:36 ` Somnath Kotur
2018-11-03 4:28 ` Somnath Kotur
2018-11-03 7:19 ` Somnath Kotur [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOBf=mst5i=OD=eaaFv+g96w5tmLHfGf5WQizj1C5ux_DEmwZA@mail.gmail.com' \
--to=somnath.kotur@broadcom.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=keith.wiles@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).