From: Joshua Washington <joshwash@google.com>
To: Jeroen de Borst <jeroendb@google.com>,
Rushil Gupta <rushilg@google.com>,
Joshua Washington <joshwash@google.com>
Cc: dev@dpdk.org, Ferruh Yigit <ferruh.yigit@amd.com>
Subject: [PATCH] net/gve: add ptype parsing to DQ format
Date: Wed, 18 Sep 2024 13:33:17 -0700 [thread overview]
Message-ID: <20240918203317.792867-1-joshwash@google.com> (raw)
Currently, the packet type is parsed as part of adding the
checksum-related ol_flags for a received packet, but the parsed
information is not added to the mbuf.
This change adds the parsed ptypes to the mbuf and updates the RX
checksum validation to rely on the mbuf instead of re-capturing the
ptype from the descriptor. This helps with compatibility with programs
which rely on the packet type value stored in the mbuf.
Signed-off-by: Joshua Washington <joshwash@google.com>
Reviewed-by: Rushil Gupta <rushilg@google.com>
---
drivers/net/gve/gve_rx_dqo.c | 62 +++++++++++++++++++++++++-----------
1 file changed, 44 insertions(+), 18 deletions(-)
diff --git a/drivers/net/gve/gve_rx_dqo.c b/drivers/net/gve/gve_rx_dqo.c
index 5efcce3312..d8e9eee4a8 100644
--- a/drivers/net/gve/gve_rx_dqo.c
+++ b/drivers/net/gve/gve_rx_dqo.c
@@ -6,6 +6,7 @@
#include "gve_ethdev.h"
#include "base/gve_adminq.h"
+#include "rte_mbuf_ptype.h"
static inline void
gve_rx_refill_dqo(struct gve_rx_queue *rxq)
@@ -75,38 +76,63 @@ gve_rx_refill_dqo(struct gve_rx_queue *rxq)
rxq->bufq_tail = next_avail;
}
-static inline uint16_t
-gve_parse_csum_ol_flags(volatile struct gve_rx_compl_desc_dqo *rx_desc,
- struct gve_priv *priv) {
- uint64_t ol_flags = 0;
- struct gve_ptype ptype =
- priv->ptype_lut_dqo->ptypes[rx_desc->packet_type];
-
+static inline void
+gve_parse_csum_ol_flags(struct rte_mbuf *rx_mbuf,
+ volatile struct gve_rx_compl_desc_dqo *rx_desc)
+{
if (!rx_desc->l3_l4_processed)
- return ol_flags;
+ return;
- if (ptype.l3_type == GVE_L3_TYPE_IPV4) {
+ if (rx_mbuf->packet_type & RTE_PTYPE_L3_IPV4) {
if (rx_desc->csum_ip_err)
- ol_flags |= RTE_MBUF_F_RX_IP_CKSUM_BAD;
+ rx_mbuf->ol_flags |= RTE_MBUF_F_RX_IP_CKSUM_BAD;
else
- ol_flags |= RTE_MBUF_F_RX_IP_CKSUM_GOOD;
+ rx_mbuf->ol_flags |= RTE_MBUF_F_RX_IP_CKSUM_GOOD;
}
if (rx_desc->csum_l4_err) {
- ol_flags |= RTE_MBUF_F_RX_L4_CKSUM_BAD;
- return ol_flags;
+ rx_mbuf->ol_flags |= RTE_MBUF_F_RX_L4_CKSUM_BAD;
+ return;
}
+ if (rx_mbuf->packet_type & RTE_PTYPE_L4_MASK)
+ rx_mbuf->ol_flags |= RTE_MBUF_F_RX_L4_CKSUM_GOOD;
+}
+
+static inline void
+gve_rx_set_mbuf_ptype(struct gve_priv *priv, struct rte_mbuf *rx_mbuf,
+ volatile struct gve_rx_compl_desc_dqo *rx_desc)
+{
+ struct gve_ptype ptype =
+ priv->ptype_lut_dqo->ptypes[rx_desc->packet_type];
+ rx_mbuf->packet_type = 0;
+
+ switch (ptype.l3_type) {
+ case GVE_L3_TYPE_IPV4:
+ rx_mbuf->packet_type |= RTE_PTYPE_L3_IPV4;
+ break;
+ case GVE_L3_TYPE_IPV6:
+ rx_mbuf->packet_type |= RTE_PTYPE_L3_IPV6;
+ break;
+ default:
+ break;
+ }
+
switch (ptype.l4_type) {
case GVE_L4_TYPE_TCP:
+ rx_mbuf->packet_type |= RTE_PTYPE_L4_TCP;
+ break;
case GVE_L4_TYPE_UDP:
+ rx_mbuf->packet_type |= RTE_PTYPE_L4_UDP;
+ break;
case GVE_L4_TYPE_ICMP:
+ rx_mbuf->packet_type |= RTE_PTYPE_L4_ICMP;
+ break;
case GVE_L4_TYPE_SCTP:
- ol_flags |= RTE_MBUF_F_RX_L4_CKSUM_GOOD;
+ rx_mbuf->packet_type |= RTE_PTYPE_L4_SCTP;
break;
default:
break;
}
- return ol_flags;
}
uint16_t
@@ -158,9 +184,9 @@ gve_rx_burst_dqo(void *rx_queue, struct rte_mbuf **rx_pkts, uint16_t nb_pkts)
rxm->pkt_len = pkt_len;
rxm->data_len = pkt_len;
rxm->port = rxq->port_id;
- rxm->ol_flags = 0;
- rxm->ol_flags |= RTE_MBUF_F_RX_RSS_HASH |
- gve_parse_csum_ol_flags(rx_desc, rxq->hw);
+ gve_rx_set_mbuf_ptype(rxq->hw, rxm, rx_desc);
+ rxm->ol_flags = RTE_MBUF_F_RX_RSS_HASH;
+ gve_parse_csum_ol_flags(rxm, rx_desc);
rxm->hash.rss = rte_le_to_cpu_32(rx_desc->hash);
rx_pkts[nb_rx++] = rxm;
--
2.46.0.662.g92d0881bb0-goog
next reply other threads:[~2024-09-18 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-18 20:33 Joshua Washington [this message]
2024-09-22 2:00 ` Ferruh Yigit
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=20240918203317.792867-1-joshwash@google.com \
--to=joshwash@google.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@amd.com \
--cc=jeroendb@google.com \
--cc=rushilg@google.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).