From: "Wiles, Keith" <keith.wiles@intel.com>
To: "Burakov, Anatoly" <anatoly.burakov@intel.com>
Cc: Somnath Kotur <somnath.kotur@broadcom.com>, dev <dev@dpdk.org>
Subject: Re: [dpdk-dev] Question about rte_manage_timer() and eal_intr_handle_interrupts
Date: Fri, 2 Nov 2018 14:37:55 +0000 [thread overview]
Message-ID: <5891119E-2F06-4467-A737-55FF37668D37@intel.com> (raw)
In-Reply-To: <3B45A79A-D782-4274-984C-DB1CD49B7252@intel.com>
> 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
next prev parent reply other threads:[~2018-11-02 14:37 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 [this message]
2018-11-03 2:36 ` Somnath Kotur
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=5891119E-2F06-4467-A737-55FF37668D37@intel.com \
--to=keith.wiles@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=somnath.kotur@broadcom.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).