DPDK patches and discussions
 help / color / mirror / Atom feed
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 08:06:13 +0530	[thread overview]
Message-ID: <CAOBf=mtAG8twiTAEQFrpfRx4iSTz6KVxMfZ+awEqwhg8r72mkQ@mail.gmail.com> (raw)
In-Reply-To: <5891119E-2F06-4467-A737-55FF37668D37@intel.com>

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
>
>

  reply	other threads:[~2018-11-03  2:36 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 [this message]
2018-11-03  4:28         ` Somnath Kotur
2018-11-03  7:19           ` Somnath Kotur

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=mtAG8twiTAEQFrpfRx4iSTz6KVxMfZ+awEqwhg8r72mkQ@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).