From: Jerin Jacob <jerinjacobk@gmail.com>
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 v3] net/cnxk: support port ID flow action item
Date: Tue, 13 Jun 2023 15:14:40 +0530 [thread overview]
Message-ID: <CALBAE1PHqCkyYKrAQoABC0bTC=VjOupDY8dXTtpbG_7058pPTQ@mail.gmail.com> (raw)
In-Reply-To: <20230613045652.228319-1-psatheesh@marvell.com>
On Tue, Jun 13, 2023 at 10:27 AM <psatheesh@marvell.com> wrote:
>
> From: Satheesh Paul <psatheesh@marvell.com>
>
> Currently PORT_ID action can redirect traffic only between
> VFs of a PF. This patch extends PORT_ID action to redirect
> traffic from one PF port to another PF port also.
>
> Signed-off-by: Satheesh Paul <psatheesh@marvell.com>
> Reviewed-by: Kiran Kumar K <kirankumark@marvell.com>
> ---
>
> See :doc:`../prog_guide/pdcp_lib` for more information.
>
> +* **Extended port ID flow action item in CNXK.**
> +
> + ``RTE_FLOW_ACTION_TYPE_PORT_ID`` action used to redirect traffic to VFs only.
> + This has been extended to redirect traffic from one PF port to another PF
> + port also.
Changed as following and applied to dpdk-next-net-mrvl/for-next-net. Thanks
+* **Updated Marvell cnxk ethdev driver.**
+
+ * Extended ``RTE_FLOW_ACTION_TYPE_PORT_ID`` to redirect traffic
across PF ports.
+
prev parent reply other threads:[~2023-06-13 9:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-09 11:18 [dpdk-dev] [PATCH] " psatheesh
2023-06-12 15:49 ` Jerin Jacob
2023-06-13 4:40 ` [dpdk-dev] [PATCH v2] " psatheesh
2023-06-13 4:56 ` [dpdk-dev] [PATCH v3] " psatheesh
2023-06-13 9:44 ` 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='CALBAE1PHqCkyYKrAQoABC0bTC=VjOupDY8dXTtpbG_7058pPTQ@mail.gmail.com' \
--to=jerinjacobk@gmail.com \
--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).