From: Fady Bader <fady@mellanox.com>
To: dev@dpdk.org
Cc: thomas@monjalon.net, talshn@mellanox.com, fady@mellanox.com,
dmitry.koziuk@gmail.com, harini.ramakrishnan@microsoft.com,
ocardona@microsoft.com, anand.rawat@intel.com,
ranjit.menon@intel.com,
Fady Bader <NTYOK.MTL.COM+fady@l-wincomp04-vm.labs.mlnx>
Subject: [dpdk-dev] [PATCH v3 0/2] eal timer split and implementation for Windows
Date: Sun, 3 May 2020 11:38:40 +0300 [thread overview]
Message-ID: <20200503083842.9312-1-fady@mellanox.com> (raw)
From: Fady Bader <NTYOK.MTL.COM+fady@l-wincomp04-vm.labs.mlnx>
This patchset splits OS dependent EAL timer functions and implements them for windows.
v2:
* fixing styles and correctness errors.
v3:
* fixing correctness, get_tsc_freq was reimplemented.
Depends-on: series-9374 ("Windows basic memory management")
Fady Bader (2):
timer: move from common to Unix directory
timer: support EAL functions on Windows
lib/librte_eal/common/eal_common_timer.c | 22 ------
lib/librte_eal/common/meson.build | 1 +
lib/librte_eal/unix/eal_timer.c | 29 +++++++
lib/librte_eal/unix/meson.build | 1 +
lib/librte_eal/windows/eal.c | 6 ++
lib/librte_eal/windows/eal_timer.c | 96 ++++++++++++++++++++++++
lib/librte_eal/windows/include/rte_os.h | 2 +
lib/librte_eal/windows/meson.build | 1 +
8 files changed, 136 insertions(+), 22 deletions(-)
create mode 100644 lib/librte_eal/unix/eal_timer.c
create mode 100644 lib/librte_eal/windows/eal_timer.c
--
2.21.0
next reply other threads:[~2020-05-03 8:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-03 8:38 Fady Bader [this message]
2020-05-03 8:38 ` [dpdk-dev] [PATCH v3 1/2] timer: move from common to Unix directory Fady Bader
2020-05-03 8:38 ` [dpdk-dev] [PATCH v3 2/2] timer: support EAL functions on Windows Fady Bader
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=20200503083842.9312-1-fady@mellanox.com \
--to=fady@mellanox.com \
--cc=NTYOK.MTL.COM+fady@l-wincomp04-vm.labs.mlnx \
--cc=anand.rawat@intel.com \
--cc=dev@dpdk.org \
--cc=dmitry.koziuk@gmail.com \
--cc=harini.ramakrishnan@microsoft.com \
--cc=ocardona@microsoft.com \
--cc=ranjit.menon@intel.com \
--cc=talshn@mellanox.com \
--cc=thomas@monjalon.net \
/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).