DPDK patches and discussions
 help / color / mirror / Atom feed
From: <skori@marvell.com>
To: Nithin Dabilpuram <ndabilpuram@marvell.com>,
	Kiran Kumar K <kirankumark@marvell.com>,
	Sunil Kumar Kori <skori@marvell.com>,
	Satha Rao <skoteshwar@marvell.com>
Cc: <dev@dpdk.org>
Subject: [PATCH v3 1/2] common/cnxk: update precolor table setup for VLAN
Date: Thu, 16 Jun 2022 17:24:01 +0530	[thread overview]
Message-ID: <20220616115402.772274-1-skori@marvell.com> (raw)
In-Reply-To: <20220616094825.761510-2-skori@marvell.com>

From: Sunil Kumar Kori <skori@marvell.com>

As per new spec in DPDK, VLAN priority is supported for
precoloring of input packet.

Depends-on: patch-23516 ("app/testpmd: support different input color method")

Signed-off-by: Sunil Kumar Kori <skori@marvell.com>
---
v2..v3:
- No changes.

v1..v2:
 - Aligned with latest input color spec.

 drivers/common/cnxk/roc_nix.h | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/drivers/common/cnxk/roc_nix.h b/drivers/common/cnxk/roc_nix.h
index aedde1c10f..98ff513cb7 100644
--- a/drivers/common/cnxk/roc_nix.h
+++ b/drivers/common/cnxk/roc_nix.h
@@ -42,6 +42,12 @@ enum roc_nix_bpf_level_flag {
 	ROC_NIX_BPF_LEVEL_F_TOP = BIT(2),
 };
 
+enum roc_nix_bpf_precolor_tbl_size {
+	ROC_NIX_BPF_PRECOLOR_TBL_SIZE_GEN = 16,
+	ROC_NIX_BPF_PRECOLOR_TBL_SIZE_VLAN = 16,
+	ROC_NIX_BPF_PRECOLOR_TBL_SIZE_DSCP = 64,
+};
+
 enum roc_nix_bpf_pc_mode {
 	ROC_NIX_BPF_PC_MODE_VLAN_INNER,
 	ROC_NIX_BPF_PC_MODE_VLAN_OUTER,
-- 
2.25.1


  reply	other threads:[~2022-06-16 11:54 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-01  9:00 [PATCH v1 1/3] " skori
2022-03-01  9:00 ` [PATCH v1 2/3] net/cnxk: support ops to update precolor VLAN table skori
2022-06-16  9:48   ` [PATCH v2 1/2] common/cnxk: update precolor table setup for VLAN skori
2022-06-16  9:48     ` [PATCH v2 2/2] net/cnxk: support ops to update precolor VLAN table skori
2022-06-16 11:54       ` skori [this message]
2022-06-16 11:54         ` [PATCH v3 " skori
2022-06-20 17:44           ` Jerin Jacob
2022-06-21  7:19             ` [EXT] " Sunil Kumar Kori
2022-06-21  7:35           ` [PATCH v4 1/2] common/cnxk: update precolor table setup for VLAN skori
2022-06-21  7:35             ` [PATCH v4 2/2] net/cnxk: support ops to update precolor VLAN table skori
2022-08-22 12:33               ` Jerin Jacob
2022-03-01  9:00 ` [PATCH v1 3/3] app/testpmd: support different input color method skori
2022-05-20 22:09   ` Ferruh Yigit
2022-05-21  7:07     ` [EXT] " Sunil Kumar Kori
2022-05-23  8:43       ` Ferruh Yigit
2022-05-24  7:35   ` [PATCH v2 1/1] " skori
2022-05-25 12:36     ` Dumitrescu, Cristian
2022-05-25 14:32       ` Sunil Kumar Kori
2022-05-25 14:37     ` skori
2022-05-25 14:41       ` Dumitrescu, Cristian
2022-05-31 15:41         ` Andrew Rybchenko
2022-06-03 13:03           ` [EXT] " Sunil Kumar Kori
2022-06-03 13:06       ` [PATCH v3 " skori
2022-06-08 12:06         ` Andrew Rybchenko
2022-06-14 10:05         ` [PATCH v4 " skori
2022-06-23 11:05           ` Andrew Rybchenko
2022-06-23 12:54             ` [EXT] " Sunil Kumar Kori
2022-06-23 12:57           ` [PATCH v5 " skori
2022-06-23 13:07             ` Sunil Kumar Kori
2022-06-24 12:44             ` Andrew Rybchenko

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=20220616115402.772274-1-skori@marvell.com \
    --to=skori@marvell.com \
    --cc=dev@dpdk.org \
    --cc=kirankumark@marvell.com \
    --cc=ndabilpuram@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).