DPDK patches and discussions
 help / color / mirror / Atom feed
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] drivers: enable keep flow rule device capability for cnxk
Date: Tue, 25 Jan 2022 04:50:41 -0500	[thread overview]
Message-ID: <87pmogrvny.fsf@mdr78.vserver.site> (raw)
In-Reply-To: <20220125041936.906026-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>
> ---
>  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 ++--
>  drivers/net/cnxk/cnxk_rte_flow.c   |  7 +++++++
>  8 files changed, 54 insertions(+), 4 deletions(-)
>
Acked-by: Ray Kinsella <mdr@ashroe.eu>

  reply	other threads:[~2022-01-25  9:50 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25  4:19 psatheesh
2022-01-25  9:50 ` Ray Kinsella [this message]
2022-02-14  4:33 ` [dpdk-dev] [PATCH v2] " psatheesh
2022-02-14 10:08   ` Ray Kinsella
2022-02-18  6:07     ` Jerin Jacob

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=87pmogrvny.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 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).