From: Ray Kinsella <mdr@ashroe.eu>
To: psatheesh@marvell.com
Cc: Nithin Dabilpuram <ndabilpuram@marvell.com>,
Kiran Kumar K <kirankumark@marvell.com>,
Sunil Kumar Kori <skori@marvell.com>,
Satha Rao <skoteshwar@marvell.com>,
dev@dpdk.org
Subject: Re: [dpdk-dev] [PATCH v2] drivers: enable keep flow rule device capability for cnxk
Date: Mon, 14 Feb 2022 05:08:57 -0500 [thread overview]
Message-ID: <87bkz9iwue.fsf@mdr78.vserver.site> (raw)
In-Reply-To: <20220214043351.1511677-1-psatheesh@marvell.com>
psatheesh@marvell.com writes:
> From: Kiran Kumar K <kirankumark@marvell.com>
>
> Adding changes to enable keep flow rule device capability.
> With this change, flow rules will be kept across device restart.
>
> Signed-off-by: Kiran Kumar K <kirankumark@marvell.com>
> Reviewed-by: Satheesh Paul <psatheesh@marvell.com>
> ---
> v2:
> * Allow creating flow rule before device start.
>
> drivers/common/cnxk/roc_npc.c | 8 ++++++++
> drivers/common/cnxk/roc_npc.h | 2 ++
> drivers/common/cnxk/roc_npc_mcam.c | 20 ++++++++++++++++++++
> drivers/common/cnxk/roc_npc_priv.h | 1 +
> drivers/common/cnxk/version.map | 1 +
> drivers/net/cnxk/cnxk_ethdev.c | 15 +++++++++++++--
> drivers/net/cnxk/cnxk_ethdev_ops.c | 4 ++--
> 7 files changed, 47 insertions(+), 4 deletions(-)
>
Acked-by: Ray Kinsella <mdr@ashroe.eu>
--
Regards, Ray K
next prev parent reply other threads:[~2022-02-14 10:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-25 4:19 [dpdk-dev] [PATCH] drivers: enable keep flow rule device capability for cnxk psatheesh
2022-01-25 9:50 ` Ray Kinsella
2022-02-14 4:33 ` [dpdk-dev] [PATCH v2] " psatheesh
2022-02-14 10:08 ` Ray Kinsella [this message]
2022-02-18 6:07 ` Jerin Jacob
-- strict thread matches above, loose matches on Subject: below --
2022-02-14 4:29 psatheesh
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=87bkz9iwue.fsf@mdr78.vserver.site \
--to=mdr@ashroe.eu \
--cc=dev@dpdk.org \
--cc=kirankumark@marvell.com \
--cc=ndabilpuram@marvell.com \
--cc=psatheesh@marvell.com \
--cc=skori@marvell.com \
--cc=skoteshwar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.