From: Thomas Monjalon <thomas@monjalon.net>
To: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
Cc: dev@dpdk.org, Khoa To <khot@microsoft.com>,
Dmitry Malloy <dmitrym@microsoft.com>,
Pallavi Kadam <pallavi.kadam@intel.com>,
Narcisa Ana Maria Vasile <navasile@linux.microsoft.com>
Subject: Re: [dpdk-dev] [PATCH v2 2/2] eal/windows: implement alarm API
Date: Wed, 14 Oct 2020 23:36:17 +0200 [thread overview]
Message-ID: <2470695.XMhHo4k61X@thomas> (raw)
In-Reply-To: <20200925234123.GB2470@linuxonhyperv3.guj3yctzbm1etfxqx2vob5hsef.xx.internal.cloudapp.net>
26/09/2020 01:41, Narcisa Ana Maria Vasile:
> On Sat, Sep 26, 2020 at 02:32:43AM +0300, Dmitry Kozlyuk wrote:
> > Implementation is based on waitable timers Win32 API. When timer is set,
> > a callback and its argument are supplied to the OS, while timer handle
> > is stored in EAL alarm list. When timer expires, OS wakes up the
> > interrupt thread and runs the callback. Upon completion it removes the
> > alarm.
> >
> > Waitable timers must be set from the thread their callback will run in,
> > eal_intr_thread_schedule() provides a way to schedule asyncronuous code
> > execution in the interrupt thread. Alarm module builds synchronous timer
> > setup on top of it.
> >
> > Windows alarms are not a type of DPDK interrupt handle and do not
> > interact with interrupt module beyond executing in the same thread.
> >
> > Signed-off-by: Dmitry Kozlyuk <dmitry.kozliuk@gmail.com>
>
> Acked-by: Narcisa Vasile <navasile@linux.microsoft.com>
Applied, thanks
prev parent reply other threads:[~2020-10-14 21:36 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-11 0:22 [dpdk-dev] [PATCH 0/2] eal/windows: implement alarms Dmitry Kozlyuk
2020-09-11 0:22 ` [dpdk-dev] [PATCH 1/2] eal/windows: add interrupt thread skeleton Dmitry Kozlyuk
2020-09-25 1:19 ` Narcisa Ana Maria Vasile
2020-09-25 6:28 ` Dmitry Kozlyuk
2020-09-11 0:22 ` [dpdk-dev] [PATCH 2/2] eal/windows: implement alarm API Dmitry Kozlyuk
2020-09-21 19:08 ` [dpdk-dev] [EXTERNAL] " Khoa To
2020-09-24 21:38 ` Dmitry Kozlyuk
2020-09-25 2:19 ` Khoa To
2020-09-25 23:32 ` [dpdk-dev] [PATCH v2 0/2] eal/windows: implement alarms Dmitry Kozlyuk
2020-09-25 23:32 ` [dpdk-dev] [PATCH v2 1/2] eal/windows: add interrupt thread skeleton Dmitry Kozlyuk
2020-09-25 23:40 ` Narcisa Ana Maria Vasile
2020-09-25 23:32 ` [dpdk-dev] [PATCH v2 2/2] eal/windows: implement alarm API Dmitry Kozlyuk
2020-09-25 23:41 ` Narcisa Ana Maria Vasile
2020-10-14 21:36 ` Thomas Monjalon [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=2470695.XMhHo4k61X@thomas \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=dmitrym@microsoft.com \
--cc=khot@microsoft.com \
--cc=navasile@linux.microsoft.com \
--cc=pallavi.kadam@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).