From: Naga Harish K S V <s.v.naga.harish.k@intel.com>
To: mdr@ashroe.eu, jerinj@marvell.com, pbhagavatula@marvell.com,
sthotton@marvell.com, erik.g.carrillo@intel.com
Cc: dev@dpdk.org
Subject: [PATCH] doc: add event timer expiry drop stat
Date: Mon, 27 Jun 2022 21:09:51 +0530 [thread overview]
Message-ID: <20220627153951.2399801-1-s.v.naga.harish.k@intel.com> (raw)
The structure ``rte_event_timer_adapter_stats`` will be
extended by adding a new field, ``evtim_drop_count``. This stat
will represent the number of times an event timer expiry is
dropped by the event timer adapter.
Signed-off-by: Naga Harish K S V <s.v.naga.harish.k@intel.com>
---
doc/guides/rel_notes/deprecation.rst | 6 ++++++
1 file changed, 6 insertions(+)
diff --git a/doc/guides/rel_notes/deprecation.rst b/doc/guides/rel_notes/deprecation.rst
index 4e5b23c53d..ab4ea67115 100644
--- a/doc/guides/rel_notes/deprecation.rst
+++ b/doc/guides/rel_notes/deprecation.rst
@@ -125,3 +125,9 @@ Deprecation Notices
applications should be updated to use the ``dmadev`` library instead,
with the underlying HW-functionality being provided by the ``ioat`` or
``idxd`` dma drivers
+
+* eventdev/timer: The structure ``rte_event_timer_adapter_stats`` will be
+ extended by adding a new field, ``evtim_drop_count``. This stat will
+ represent the number of times an event timer expiry is dropped
+ by the timer adapter. This field will be used by a future patch adding
+ support for periodic mode to the software timer adapter in DPDK 22.11.
--
2.25.1
next reply other threads:[~2022-06-27 16:13 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 15:39 Naga Harish K S V [this message]
2022-06-28 2:34 ` [PATCH v2] " Naga Harish K S V
2022-07-12 11:52 ` Jerin Jacob
2022-07-12 15:08 ` Hemant Agrawal
2022-07-14 11:20 ` Van Haaren, Harry
2022-07-17 11:43 ` Thomas Monjalon
2022-06-30 19:13 ` [PATCH] " Carrillo, Erik G
2022-07-11 14:55 ` Jerin Jacob
2022-07-12 15:07 ` Hemant Agrawal
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=20220627153951.2399801-1-s.v.naga.harish.k@intel.com \
--to=s.v.naga.harish.k@intel.com \
--cc=dev@dpdk.org \
--cc=erik.g.carrillo@intel.com \
--cc=jerinj@marvell.com \
--cc=mdr@ashroe.eu \
--cc=pbhagavatula@marvell.com \
--cc=sthotton@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).