From: Shijith Thotton <sthotton@marvell.com>
To: Erik Gabriel Carrillo <erik.g.carrillo@intel.com>
Cc: Shijith Thotton <sthotton@marvell.com>,
Pavan Nikhilesh <pbhagavatula@marvell.com>,
Jerin Jacob <jerinj@marvell.com>, <dev@dpdk.org>
Subject: [dpdk-dev] [PATCH v3 0/3] periodic mode for event timer adapter
Date: Wed, 17 Mar 2021 13:34:18 +0530 [thread overview]
Message-ID: <cover.1615967694.git.sthotton@marvell.com> (raw)
In-Reply-To: <cover.1615738894.git.sthotton@marvell.com>
Arming periodic timers are not supported by the event timer adapter
right now. This series adds that support. A timer adapter configured in
periodic mode can be used to arm periodic timers.
First patch adds a flag to expose periodic mode capability of an adapter
and flag to configure the adapter in periodic mode. Second one adds unit
tests for periodic mode. Third one is a hardware implementation of the
feature.
v3:
- Text and checkpatch related corrections.
v2:
- Updated rst and doxygen documentation.
Shijith Thotton (3):
eventdev: introduce adapter flags for periodic mode
test/event: add unit tests for periodic timer
event/octeontx2: add timer periodic mode support
app/test/test_event_timer_adapter.c | 138 ++++++++++++++++--
doc/guides/prog_guide/event_timer_adapter.rst | 16 +-
drivers/event/octeontx2/otx2_tim_evdev.c | 29 +++-
drivers/event/octeontx2/otx2_tim_evdev.h | 1 +
lib/librte_eventdev/rte_event_timer_adapter.h | 13 ++
lib/librte_eventdev/rte_eventdev.h | 3 +
6 files changed, 181 insertions(+), 19 deletions(-)
--
2.25.1
next prev parent reply other threads:[~2021-03-17 8:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-08 20:45 [dpdk-dev] [PATCH " Shijith Thotton
2021-03-08 20:45 ` [dpdk-dev] [PATCH 1/3] eventdev: introduce adapter flags for periodic mode Shijith Thotton
2021-03-09 20:04 ` Carrillo, Erik G
2021-03-10 9:14 ` Shijith Thotton
2021-03-11 20:47 ` Carrillo, Erik G
2021-03-12 15:30 ` Carrillo, Erik G
2021-03-14 16:49 ` Shijith Thotton
2021-03-08 20:45 ` [dpdk-dev] [PATCH 2/3] test/event: add unit tests for periodic timer Shijith Thotton
2021-03-08 20:45 ` [dpdk-dev] [PATCH 3/3] event/octeontx2: add timer periodic mode support Shijith Thotton
2021-03-14 16:45 ` [dpdk-dev] [PATCH v2 0/3] periodic mode for event timer adapter Shijith Thotton
2021-03-14 16:45 ` [dpdk-dev] [PATCH v2 1/3] eventdev: introduce adapter flags for periodic mode Shijith Thotton
2021-03-16 19:04 ` Carrillo, Erik G
2021-03-17 6:10 ` Shijith Thotton
2021-03-14 16:45 ` [dpdk-dev] [PATCH v2 2/3] test/event: add unit tests for periodic timer Shijith Thotton
2021-03-14 16:45 ` [dpdk-dev] [PATCH v2 3/3] event/octeontx2: add timer periodic mode support Shijith Thotton
2021-03-17 8:04 ` Shijith Thotton [this message]
2021-03-17 8:04 ` [dpdk-dev] [PATCH v3 1/3] eventdev: introduce adapter flags for periodic mode Shijith Thotton
2021-03-17 18:07 ` Carrillo, Erik G
2021-03-22 9:50 ` Jerin Jacob
2021-03-17 8:04 ` [dpdk-dev] [PATCH v3 2/3] test/event: add unit tests for periodic timer Shijith Thotton
2021-03-17 18:11 ` Carrillo, Erik G
2021-03-17 8:04 ` [dpdk-dev] [PATCH v3 3/3] event/octeontx2: add timer periodic mode support Shijith Thotton
2021-03-21 14:43 ` Pavan Nikhilesh Bhagavatula
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=cover.1615967694.git.sthotton@marvell.com \
--to=sthotton@marvell.com \
--cc=dev@dpdk.org \
--cc=erik.g.carrillo@intel.com \
--cc=jerinj@marvell.com \
--cc=pbhagavatula@marvell.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).