From: "Van Haaren, Harry" <harry.van.haaren@intel.com>
To: "hemant.agrawal@nxp.com" <hemant.agrawal@nxp.com>,
"dev@dpdk.org" <dev@dpdk.org>
Subject: RE: [PATCH v2] doc: add event timer expiry drop stat
Date: Thu, 14 Jul 2022 11:20:05 +0000 [thread overview]
Message-ID: <BN0PR11MB5712DCBAAD5D2E7F78F99D87D7889@BN0PR11MB5712.namprd11.prod.outlook.com> (raw)
In-Reply-To: <caf9816e-b4da-6d88-b813-1c2335d7c720@oss.nxp.com>
> -----Original Message-----
> From: Hemant Agrawal <hemant.agrawal@oss.nxp.com>
> Sent: Tuesday, July 12, 2022 4:08 PM
> To: dev@dpdk.org
> Subject: Re: [PATCH v2] doc: add event timer expiry drop stat
>
>
> On 7/12/2022 5:22 PM, Jerin Jacob wrote:
> > 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>
>
> Acked-by: Hemant Agrawal <hemant.agrawal@nxp.com>
Adding a statistic seems reasonable;
Acked-by: Harry van Haaren <harry.van.haaren@intel.com>
next prev parent reply other threads:[~2022-07-14 11:20 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
2022-07-12 15:08 ` Hemant Agrawal
2022-07-14 11:20 ` Van Haaren, Harry [this message]
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=BN0PR11MB5712DCBAAD5D2E7F78F99D87D7889@BN0PR11MB5712.namprd11.prod.outlook.com \
--to=harry.van.haaren@intel.com \
--cc=dev@dpdk.org \
--cc=hemant.agrawal@nxp.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).