DPDK patches and discussions
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Srikanth Yalavarthi <syalavarthi@marvell.com>
Cc: dev@dpdk.org, syalavarthi@marvell.com, sshankarnara@marvell.com,
	aprabhu@marvell.com, ptakkar@marvell.com
Subject: Re: [PATCH v1 0/5] Implementation of revised ML xstats spec
Date: Tue, 06 Jun 2023 15:40:04 +0200	[thread overview]
Message-ID: <64851000.3F2A3RajZp@thomas> (raw)
In-Reply-To: <20230423051403.31971-1-syalavarthi@marvell.com>

23/04/2023 07:13, Srikanth Yalavarthi:
> This series of patches introduces revised xstats specification for ML
> device. The revised xstats spec is based on eventdev xstats and supports
> DEVICE and MODEL modes to get xstats. This enables retrieving xstats for
> device and each model separately.
> 
> 
> Srikanth Yalavarthi (5):
>   mldev: remove xstats APIs from library
>   mldev: introduce revised xstats
>   mldev: implement xstats library functions
>   app/mldev: enable reporting xstats
>   ml/cnxk: implement xstats driver functions

Applied, thanks.

Note: did one small fix in a meson file and squashed implem with API




      parent reply	other threads:[~2023-06-06 13:40 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-23  5:13 Srikanth Yalavarthi
2023-04-23  5:13 ` [PATCH v1 1/5] mldev: remove xstats APIs from library Srikanth Yalavarthi
2023-04-23  5:14 ` [PATCH v1 2/5] mldev: introduce revised xstats Srikanth Yalavarthi
2023-04-23  5:14 ` [PATCH v1 3/5] mldev: implement xstats library functions Srikanth Yalavarthi
2023-04-23  5:14 ` [PATCH v1 4/5] app/mldev: enable reporting xstats Srikanth Yalavarthi
2023-04-23  5:14 ` [PATCH v1 5/5] ml/cnxk: implement xstats driver functions Srikanth Yalavarthi
2023-06-06 13:40 ` Thomas Monjalon [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=64851000.3F2A3RajZp@thomas \
    --to=thomas@monjalon.net \
    --cc=aprabhu@marvell.com \
    --cc=dev@dpdk.org \
    --cc=ptakkar@marvell.com \
    --cc=sshankarnara@marvell.com \
    --cc=syalavarthi@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).