From: Hemant Agrawal <hemant.agrawal@oss.nxp.com>
To: Jerin Jacob <jerinjacobk@gmail.com>,
"Carrillo, Erik G" <erik.g.carrillo@intel.com>
Cc: "Naga Harish K, S V" <s.v.naga.harish.k@intel.com>,
"mdr@ashroe.eu" <mdr@ashroe.eu>,
"jerinj@marvell.com" <jerinj@marvell.com>,
"pbhagavatula@marvell.com" <pbhagavatula@marvell.com>,
"sthotton@marvell.com" <sthotton@marvell.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: Re: [PATCH] doc: add event timer expiry drop stat
Date: Tue, 12 Jul 2022 20:37:21 +0530 [thread overview]
Message-ID: <632e2b1f-deda-946c-6c8c-cb294e2bebcc@oss.nxp.com> (raw)
In-Reply-To: <CALBAE1PpsrZsXmHcr+uP9A3GVJ9yL-q4tEPb=o6Lz8mfb=0U8g@mail.gmail.com>
On 7/11/2022 8:25 PM, Jerin Jacob wrote:
> On Fri, Jul 1, 2022 at 12:43 AM Carrillo, Erik G
> <erik.g.carrillo@intel.com> wrote:
>>> -----Original Message-----
>>> From: Naga Harish K, S V <s.v.naga.harish.k@intel.com>
>>> Sent: Monday, June 27, 2022 10:40 AM
>>> To: mdr@ashroe.eu; jerinj@marvell.com; pbhagavatula@marvell.com;
>>> sthotton@marvell.com; Carrillo, Erik G <erik.g.carrillo@intel.com>
>>> Cc: dev@dpdk.org
>>> Subject: [PATCH] doc: add event timer expiry drop stat
>>>
>>> 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>
>> Reviewed-by: Erik Gabriel Carrillo <erik.g.carrillo@intel.com>
> Acked-by: Jerin Jacob <jerinj@marvell.com>
Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
prev parent reply other threads:[~2022-07-12 15:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-27 15:39 Naga Harish K S V
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 [this message]
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=632e2b1f-deda-946c-6c8c-cb294e2bebcc@oss.nxp.com \
--to=hemant.agrawal@oss.nxp.com \
--cc=dev@dpdk.org \
--cc=erik.g.carrillo@intel.com \
--cc=hemant.agrawal@nxp.com \
--cc=jerinj@marvell.com \
--cc=jerinjacobk@gmail.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).