From: Fady Bader <fady@mellanox.com>
To: dev@dpdk.org
Cc: fady@mellanox.com, thomas@monjalon.net, tbashar@mellanox.com,
talshn@mellanox.com, yohadt@mellanox.com,
dmitry.kozliuk@gmail.com, harini.ramakrishnan@microsoft.com,
ocardona@microsoft.com, pallavi.kadam@intel.com,
ranjit.menon@intel.com
Subject: [dpdk-dev] [PATCH v10 0/2] eal timer split and implementation for Windows
Date: Thu, 18 Jun 2020 09:55:20 +0300 [thread overview]
Message-ID: <20200618065522.22884-1-fady@mellanox.com> (raw)
In-Reply-To: <20200423144350.4016-2-fady@mellanox.com>
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.
v4:
* rebasing to the new version of "Windows basic memory management" series.
* fixing styles and correctness errors.
v5:
* breaking the dependency on "Windows basic memory management" series.
* fixing correctness errors and warnings.
v6:
* fixing styles and correctness errors.
v7:
* fixing make errors.
v8:
* fixing error handling issue.
* removed unneded headers.
v9:
* rebasing to current master.
* fixing correctness issue.
v10:
* fixing correctness issue.
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/freebsd/Makefile | 1 +
lib/librte_eal/linux/Makefile | 1 +
lib/librte_eal/unix/eal_unix_timer.c | 29 ++++++++++
lib/librte_eal/unix/meson.build | 1 +
lib/librte_eal/windows/eal.c | 6 +++
lib/librte_eal/windows/eal_timer.c | 93 ++++++++++++++++++++++++++++++++
lib/librte_eal/windows/include/rte_os.h | 2 +
lib/librte_eal/windows/meson.build | 1 +
10 files changed, 135 insertions(+), 22 deletions(-)
create mode 100644 lib/librte_eal/unix/eal_unix_timer.c
create mode 100644 lib/librte_eal/windows/eal_timer.c
--
2.16.1.windows.4
next prev parent reply other threads:[~2020-06-18 6:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-23 14:43 [dpdk-dev] [PATCH " Fady Bader
2020-04-23 14:43 ` [dpdk-dev] [PATCH 1/2] timer: move from common to Unix directory Fady Bader
2020-06-17 9:39 ` [dpdk-dev] [PATCH v9 0/2] eal timer split and implementation for Windows Fady Bader
2020-06-17 9:39 ` [dpdk-dev] [PATCH v9 1/2] timer: move from common to Unix directory Fady Bader
2020-06-17 9:39 ` [dpdk-dev] [PATCH v9 2/2] timer: support EAL functions on Windows Fady Bader
2020-06-17 22:15 ` Ranjit Menon
2020-06-18 7:56 ` Fady Bader
2020-06-18 6:55 ` Fady Bader [this message]
2020-06-18 6:55 ` [dpdk-dev] [PATCH v10 1/2] timer: move from common to Unix directory Fady Bader
2020-06-18 6:55 ` [dpdk-dev] [PATCH v10 2/2] timer: support EAL functions on Windows Fady Bader
2020-06-18 19:32 ` [dpdk-dev] [PATCH v10 0/2] eal timer split and implementation for Windows Ranjit Menon
2020-06-23 16:19 ` Thomas Monjalon
2020-04-23 14:43 ` [dpdk-dev] [PATCH 2/2] timer: support EAL functions on Windows Fady Bader
2020-04-23 15:18 ` Dmitry Kozlyuk
2020-04-24 21:32 ` Dmitry Kozlyuk
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=20200618065522.22884-1-fady@mellanox.com \
--to=fady@mellanox.com \
--cc=dev@dpdk.org \
--cc=dmitry.kozliuk@gmail.com \
--cc=harini.ramakrishnan@microsoft.com \
--cc=ocardona@microsoft.com \
--cc=pallavi.kadam@intel.com \
--cc=ranjit.menon@intel.com \
--cc=talshn@mellanox.com \
--cc=tbashar@mellanox.com \
--cc=thomas@monjalon.net \
--cc=yohadt@mellanox.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).