From: Jerin Jacob <jerinjacobk@gmail.com>
To: Ganapati Kundapura <ganapati.kundapura@intel.com>
Cc: dev@dpdk.org, jay.jayatheerthan@intel.com, s.v.naga.harish.k@intel.com
Subject: Re: [PATCH v1 1/1] eventdev/eth_rx: add event buf size and count in telemetry
Date: Tue, 4 Apr 2023 16:19:24 +0530 [thread overview]
Message-ID: <CALBAE1OaC7vZu1nxmm+12Um5HDB=v-rOM7uL_Uyup3TqWsAZhQ@mail.gmail.com> (raw)
In-Reply-To: <CALBAE1OwmX1MAAFniT3ey3+Dyb3TDS=c5oRf3jquZ3bVkWd0EQ@mail.gmail.com>
On Tue, Apr 4, 2023 at 4:19 PM Jerin Jacob <jerinjacobk@gmail.com> wrote:
>
> On Thu, Mar 23, 2023 at 2:28 PM Ganapati Kundapura
> <ganapati.kundapura@intel.com> wrote:
> >
> > rx_event_buf_count and rx_event_buf_size is added to structure
> > rte_event_eth_rx_adapter_stats but they are not displayed in
> > rxa_stats telemetry handler.
> >
> > Updated handle_rxa_stats() to display rx_event_buf_count and
> > rx_event_buf_size.
> >
> > Signed-off-by: Ganapati Kundapura <ganapati.kundapura@intel.com>
>
>
> Acked-by: Jerin Jacob <jerinj@marvell.com>
Applied to dpdk-next-net-eventdev/for-main. Thanks
>
>
> >
> > diff --git a/lib/eventdev/rte_event_eth_rx_adapter.c b/lib/eventdev/rte_event_eth_rx_adapter.c
> > index c1cd124..07d8235 100644
> > --- a/lib/eventdev/rte_event_eth_rx_adapter.c
> > +++ b/lib/eventdev/rte_event_eth_rx_adapter.c
> > @@ -3597,6 +3597,8 @@ handle_rxa_stats(const char *cmd __rte_unused,
> > RXA_ADD_DICT(rx_adptr_stats, rx_enq_block_cycles);
> > RXA_ADD_DICT(rx_adptr_stats, rx_enq_end_ts);
> > RXA_ADD_DICT(rx_adptr_stats, rx_intr_packets);
> > + RXA_ADD_DICT(rx_adptr_stats, rx_event_buf_count);
> > + RXA_ADD_DICT(rx_adptr_stats, rx_event_buf_size);
> >
> > return 0;
> > }
> > --
> > 2.6.4
> >
prev parent reply other threads:[~2023-04-04 10:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 8:58 Ganapati Kundapura
2023-04-04 10:49 ` Jerin Jacob
2023-04-04 10:49 ` Jerin Jacob [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='CALBAE1OaC7vZu1nxmm+12Um5HDB=v-rOM7uL_Uyup3TqWsAZhQ@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=ganapati.kundapura@intel.com \
--cc=jay.jayatheerthan@intel.com \
--cc=s.v.naga.harish.k@intel.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).