DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob Kollanukkaran <jerinj@marvell.com>
To: Kiran Kumar Kokkilagadda <kirankumark@marvell.com>,
	"dev@dpdk.org" <dev@dpdk.org>
Cc: Kiran Kumar Kokkilagadda <kirankumark@marvell.com>
Subject: Re: [dpdk-dev] [PATCH] net/octeontx2: add PF and VF action support
Date: Mon, 8 Jul 2019 04:55:43 +0000	[thread overview]
Message-ID: <BYAPR18MB24240F3587159B8F03AA09ADC8F60@BYAPR18MB2424.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20190708033615.26373-1-kirankumark@marvell.com>

> -----Original Message-----
> From: dev <dev-bounces@dpdk.org> On Behalf Of
> kirankumark@marvell.com
> Sent: Monday, July 8, 2019 9:06 AM
> To: dev@dpdk.org
> Cc: Kiran Kumar Kokkilagadda <kirankumark@marvell.com>
> Subject: [dpdk-dev] [PATCH] net/octeontx2: add PF and VF action support
> 
> From: Kiran Kumar K <kirankumark@marvell.com>
> 
> Adding PF and VF action support for octeontx2 Flow.
> If RTE_FLOW_ACTION_TYPE_PF action is set from VF, then the packet will be
> sent to the parent PF.
> If RTE_FLOW_ACTION_TYPE_VF action is set and original is specified, then
> the packet will be sent to the original VF, otherwise the packet will be sent to
> the VF specified in the vf_id.
> 
> Signed-off-by: Kiran Kumar K <kirankumark@marvell.com>

Acked-by: Jerin Jacob <jerinj@marvell.com>

> ---
>  doc/guides/nics/octeontx2.rst           |  4 ++++
>  drivers/net/octeontx2/otx2_flow.h       |  2 ++
>  drivers/net/octeontx2/otx2_flow_parse.c | 32
> ++++++++++++++++++++++---
>  3 files changed, 35 insertions(+), 3 deletions(-)
> 

  reply	other threads:[~2019-07-08  4:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-08  3:36 kirankumark
2019-07-08  4:55 ` Jerin Jacob Kollanukkaran [this message]
2019-07-09 11:01   ` Jerin Jacob Kollanukkaran

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=BYAPR18MB24240F3587159B8F03AA09ADC8F60@BYAPR18MB2424.namprd18.prod.outlook.com \
    --to=jerinj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=kirankumark@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).