DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinjacobk@gmail.com>
To: Naga Harish K S V <s.v.naga.harish.k@intel.com>
Cc: dpdk-dev <dev@dpdk.org>,
	Erik Gabriel Carrillo <erik.g.carrillo@intel.com>,
	Jerin Jacob <jerinj@marvell.com>, Ray Kinsella <mdr@ashroe.eu>,
	 Pavan Nikhilesh <pbhagavatula@marvell.com>,
	Shijith Thotton <sthotton@marvell.com>
Subject: Re: [PATCH v2] doc: add event timer expiry drop stat
Date: Tue, 12 Jul 2022 17:22:46 +0530	[thread overview]
Message-ID: <CALBAE1MA8=fC_YUbRJTcZ1GwN=wSwpMKZuvAxJ+YAnEZ+0Nxjw@mail.gmail.com> (raw)
In-Reply-To: <20220628023458.2401715-1-s.v.naga.harish.k@intel.com>

On Tue, Jun 28, 2022 at 8:38 AM Naga Harish K S V
<s.v.naga.harish.k@intel.com> wrote:
>
> 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 event
> is dropped by the event timer adapter.
>
> Signed-off-by: Naga Harish K S V <s.v.naga.harish.k@intel.com>


Acked-by: Jerin Jacob <jerinj@marvell.com>

> ---
> v2:
> * update commit message
> ---
>  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..597a457a37 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 event 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
>

  reply	other threads:[~2022-07-12 11:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-27 15:39 [PATCH] " Naga Harish K S V
2022-06-28  2:34 ` [PATCH v2] " Naga Harish K S V
2022-07-12 11:52   ` Jerin Jacob [this message]
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='CALBAE1MA8=fC_YUbRJTcZ1GwN=wSwpMKZuvAxJ+YAnEZ+0Nxjw@mail.gmail.com' \
    --to=jerinjacobk@gmail.com \
    --cc=dev@dpdk.org \
    --cc=erik.g.carrillo@intel.com \
    --cc=jerinj@marvell.com \
    --cc=mdr@ashroe.eu \
    --cc=pbhagavatula@marvell.com \
    --cc=s.v.naga.harish.k@intel.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).