From: Jerin Jacob <jerinjacobk@gmail.com>
To: pbhagavatula@marvell.com
Cc: jerinj@marvell.com, Shijith Thotton <sthotton@marvell.com>, dev@dpdk.org
Subject: Re: [PATCH] event/cnxk: fix missing xstats ops registration
Date: Fri, 30 Sep 2022 12:46:24 +0530 [thread overview]
Message-ID: <CALBAE1NyF-st5hYMGkkad8C3Dbfxen1meGvE29FO_466N5et9Q@mail.gmail.com> (raw)
In-Reply-To: <20220927153151.7860-1-pbhagavatula@marvell.com>
On Tue, Sep 27, 2022 at 9:02 PM <pbhagavatula@marvell.com> wrote:
>
> From: Pavan Nikhilesh <pbhagavatula@marvell.com>
>
> Fix missing xstats ops registration when initializing event device.
>
> Fixes: b5a52c9d97e2 ("event/cnxk: add event port and queue xstats")
>
> Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
Applied to dpdk-next-net-eventdev/for-main. Thanks
> ---
> drivers/event/cnxk/cn10k_eventdev.c | 4 ++++
> drivers/event/cnxk/cn9k_eventdev.c | 4 ++++
> 2 files changed, 8 insertions(+)
>
> diff --git a/drivers/event/cnxk/cn10k_eventdev.c b/drivers/event/cnxk/cn10k_eventdev.c
> index fc55bda503..4ba5314fda 100644
> --- a/drivers/event/cnxk/cn10k_eventdev.c
> +++ b/drivers/event/cnxk/cn10k_eventdev.c
> @@ -1110,6 +1110,10 @@ static struct eventdev_ops cn10k_sso_dev_ops = {
> .crypto_adapter_queue_pair_add = cn10k_crypto_adapter_qp_add,
> .crypto_adapter_queue_pair_del = cn10k_crypto_adapter_qp_del,
>
> + .xstats_get = cnxk_sso_xstats_get,
> + .xstats_reset = cnxk_sso_xstats_reset,
> + .xstats_get_names = cnxk_sso_xstats_get_names,
> +
> .dump = cnxk_sso_dump,
> .dev_start = cn10k_sso_start,
> .dev_stop = cn10k_sso_stop,
> diff --git a/drivers/event/cnxk/cn9k_eventdev.c b/drivers/event/cnxk/cn9k_eventdev.c
> index 29c952c791..764963db85 100644
> --- a/drivers/event/cnxk/cn9k_eventdev.c
> +++ b/drivers/event/cnxk/cn9k_eventdev.c
> @@ -1199,6 +1199,10 @@ static struct eventdev_ops cn9k_sso_dev_ops = {
> .crypto_adapter_queue_pair_add = cn9k_crypto_adapter_qp_add,
> .crypto_adapter_queue_pair_del = cn9k_crypto_adapter_qp_del,
>
> + .xstats_get = cnxk_sso_xstats_get,
> + .xstats_reset = cnxk_sso_xstats_reset,
> + .xstats_get_names = cnxk_sso_xstats_get_names,
> +
> .dump = cnxk_sso_dump,
> .dev_start = cn9k_sso_start,
> .dev_stop = cn9k_sso_stop,
> --
> 2.25.1
>
prev parent reply other threads:[~2022-09-30 7:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-27 15:31 pbhagavatula
2022-09-30 7:16 ` 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=CALBAE1NyF-st5hYMGkkad8C3Dbfxen1meGvE29FO_466N5et9Q@mail.gmail.com \
--to=jerinjacobk@gmail.com \
--cc=dev@dpdk.org \
--cc=jerinj@marvell.com \
--cc=pbhagavatula@marvell.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).