DPDK patches and discussions
 help / color / mirror / Atom feed
From: <pbhagavatula@marvell.com>
To: <jerinj@marvell.com>, John McNamara <john.mcnamara@intel.com>,
	"Marko Kovacevic" <marko.kovacevic@intel.com>,
	Thomas Monjalon <thomas@monjalon.net>,
	Ferruh Yigit <ferruh.yigit@intel.com>,
	Andrew Rybchenko <arybchenko@solarflare.com>
Cc: <dev@dpdk.org>, Pavan Nikhilesh <pbhagavatula@marvell.com>
Subject: [dpdk-dev]  [RFC 1/3] ethdev: add ptype as an Rx offload
Date: Tue, 6 Aug 2019 13:32:02 +0530	[thread overview]
Message-ID: <20190806080206.1572-2-pbhagavatula@marvell.com> (raw)
In-Reply-To: <20190806080206.1572-1-pbhagavatula@marvell.com>

From: Pavan Nikhilesh <pbhagavatula@marvell.com>

Add ptype to DEV_RX_OFFLOAD_* flags which can be used to enable/disable
packet type parsing.

Signed-off-by: Pavan Nikhilesh <pbhagavatula@marvell.com>
---
 doc/guides/nics/features.rst   | 3 +++
 lib/librte_ethdev/rte_ethdev.h | 1 +
 2 files changed, 4 insertions(+)

diff --git a/doc/guides/nics/features.rst b/doc/guides/nics/features.rst
index 6f8cac2c8..6b222b270 100644
--- a/doc/guides/nics/features.rst
+++ b/doc/guides/nics/features.rst
@@ -662,6 +662,9 @@ Packet type parsing
 
 Supports packet type parsing and returns a list of supported types.
 
+* **[uses]       rte_eth_rxconf,rte_eth_rxmpde**: ``offloads:DEV_RX_OFFLOAD_PTYPE``.
+* **[provides]   mbuf**: ``mbuf.packet_type``.
+* **[provides]   rte_eth_dev_info**: ``rx_offload_capa,rx_queue_offload_capa:DEV_RX_OFFLOAD_PTYPE``.
 * **[implements] eth_dev_ops**: ``dev_supported_ptypes_get``.
 * **[related]    API**: ``rte_eth_dev_get_supported_ptypes()``.
 
diff --git a/lib/librte_ethdev/rte_ethdev.h b/lib/librte_ethdev/rte_ethdev.h
index dc6596bc9..888b766d4 100644
--- a/lib/librte_ethdev/rte_ethdev.h
+++ b/lib/librte_ethdev/rte_ethdev.h
@@ -1013,6 +1013,7 @@ struct rte_eth_conf {
 #define DEV_RX_OFFLOAD_KEEP_CRC		0x00010000
 #define DEV_RX_OFFLOAD_SCTP_CKSUM	0x00020000
 #define DEV_RX_OFFLOAD_OUTER_UDP_CKSUM  0x00040000
+#define DEV_RX_OFFLOAD_PTYPE		0x00080000
 
 #define DEV_RX_OFFLOAD_CHECKSUM (DEV_RX_OFFLOAD_IPV4_CKSUM | \
 				 DEV_RX_OFFLOAD_UDP_CKSUM | \
-- 
2.17.1


  reply	other threads:[~2019-08-06  8:02 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-06  8:02 [dpdk-dev] [RFC 0/3] ethdev: add ptype as " pbhagavatula
2019-08-06  8:02 ` pbhagavatula [this message]
2019-08-06  9:00   ` [dpdk-dev] [RFC 1/3] ethdev: add ptype as an " Andrew Rybchenko
2019-08-06 14:31     ` [dpdk-dev] [EXT] " Pavan Nikhilesh Bhagavatula
2019-08-06 15:45       ` Stephen Hemminger
2019-08-06 18:03         ` Andrew Rybchenko
2019-08-06  8:02 ` [dpdk-dev] [RFC 2/3] net: update Rx offload capabilities pbhagavatula
2019-08-06  8:02 ` [dpdk-dev] [RFC 3/3] examples: add Rx ptype offload pbhagavatula
2019-08-06  9:20   ` Ananyev, Konstantin
2019-08-06 13:57     ` Pavan Nikhilesh Bhagavatula
2019-08-06  8:19 ` [dpdk-dev] [RFC 0/3] ethdev: add ptype as Rx offload Hemant Agrawal
2019-08-06  8:47   ` Pavan Nikhilesh Bhagavatula
2019-08-06  9:06     ` Andrew Rybchenko
2019-08-06 23:15       ` Stephen Hemminger

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=20190806080206.1572-2-pbhagavatula@marvell.com \
    --to=pbhagavatula@marvell.com \
    --cc=arybchenko@solarflare.com \
    --cc=dev@dpdk.org \
    --cc=ferruh.yigit@intel.com \
    --cc=jerinj@marvell.com \
    --cc=john.mcnamara@intel.com \
    --cc=marko.kovacevic@intel.com \
    --cc=thomas@monjalon.net \
    /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).