DPDK patches and discussions
 help / color / mirror / Atom feed
From: Jerin Jacob <jerinj@marvell.com>
To: Satheesh Paul Antonysamy <psatheesh@marvell.com>,
	Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>,
	Kiran Kumar Kokkilagadda <kirankumark@marvell.com>,
	Sunil Kumar Kori <skori@marvell.com>,
	Satha Koteswara Rao Kottidi <skoteshwar@marvell.com>,
	Harman Kalra <hkalra@marvell.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
	Satheesh Paul Antonysamy <psatheesh@marvell.com>
Subject: RE: [EXTERNAL] [dpdk-dev] [PATCH v4 1/2] common/cnxk: support NPC flow on cn20k
Date: Tue, 4 Feb 2025 15:00:53 +0000	[thread overview]
Message-ID: <BY3PR18MB47852DF9E513C3EF192CBEDFC8F42@BY3PR18MB4785.namprd18.prod.outlook.com> (raw)
In-Reply-To: <20250123055247.3784086-1-psatheesh@marvell.com>



> -----Original Message-----
> From: psatheesh@marvell.com <psatheesh@marvell.com>
> Sent: Thursday, January 23, 2025 11:23 AM
> To: Nithin Kumar Dabilpuram <ndabilpuram@marvell.com>; Kiran Kumar
> Kokkilagadda <kirankumark@marvell.com>; Sunil Kumar Kori
> <skori@marvell.com>; Satha Koteswara Rao Kottidi
> <skoteshwar@marvell.com>; Harman Kalra <hkalra@marvell.com>
> Cc: dev@dpdk.org; Satheesh Paul Antonysamy <psatheesh@marvell.com>
> Subject: [EXTERNAL] [dpdk-dev] [PATCH v4 1/2] common/cnxk: support NPC
> flow on cn20k
> 
> From: Satheesh Paul <psatheesh@ marvell. com> ROC changes to support NPC
> flow on cn20k. Signed-off-by: Satheesh Paul <psatheesh@ marvell. com>
> Reviewed-by: Kiran Kumar K <kirankumark@ marvell. com> --- v2: * Fixed
> generic platform
> 
> From: Satheesh Paul <psatheesh@marvell.com>
> 
> ROC changes to support NPC flow on cn20k.
> 
> Signed-off-by: Satheesh Paul <psatheesh@marvell.com>
> Reviewed-by: Kiran Kumar K <kirankumark@marvell.com>
> ---
_LEN];
> +};
> +
> +struct npc_get_field_hash_info_req {
> +	struct mbox_msghdr hdr;
> +	uint8_t intf;

1)Looks like __io tag is missing
2)Please update the release note for this feature(rte_flow support for cn20k)

> +};
> +
>


  parent reply	other threads:[~2025-02-04 15:00 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-10-21  4:01 [dpdk-dev] [PATCH " psatheesh
2024-10-21  4:01 ` [dpdk-dev] [PATCH 2/2] net/cnxk: support rte " psatheesh
2024-10-21 17:09   ` Stephen Hemminger
2024-10-29  7:31 ` [dpdk-dev] [PATCH v2 1/2] common/cnxk: support NPC " psatheesh
2024-10-29  7:31   ` [dpdk-dev] [PATCH v2 2/2] net/cnxk: support rte " psatheesh
2024-11-04 11:29     ` Jerin Jacob
2024-11-12  9:58 ` [dpdk-dev] [PATCH v3 1/2] common/cnxk: support NPC " psatheesh
2024-11-12  9:58   ` [dpdk-dev] [PATCH v3 2/2] net/cnxk: support rte " psatheesh
2025-01-22 12:33     ` [EXTERNAL] " Jerin Jacob
2025-01-23  5:48       ` Satheesh Paul Antonysamy
2025-01-23  5:52 ` [dpdk-dev] [PATCH v4 1/2] common/cnxk: support NPC " psatheesh
2025-01-23  5:52   ` [dpdk-dev] [PATCH v4 2/2] net/cnxk: support rte " psatheesh
2025-02-04 15:00   ` Jerin Jacob [this message]
2025-02-05  5:42 ` [dpdk-dev] [PATCH v5 1/2] common/cnxk: support NPC " psatheesh
2025-02-05  5:42   ` [dpdk-dev] [PATCH v5 2/2] net/cnxk: support rte " 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=BY3PR18MB47852DF9E513C3EF192CBEDFC8F42@BY3PR18MB4785.namprd18.prod.outlook.com \
    --to=jerinj@marvell.com \
    --cc=dev@dpdk.org \
    --cc=hkalra@marvell.com \
    --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).