From: "Morten Brørup" <mb@smartsharesystems.com>
To: "David Marchand" <david.marchand@redhat.com>
Cc: <dev@dpdk.org>
Subject: RE: [PATCH] mbuf: dump Tx offload metadata
Date: Fri, 31 Oct 2025 14:28:24 +0100 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35F65523@smartserver.smartshare.dk> (raw)
In-Reply-To: <20251031131159.1199221-1-david.marchand@redhat.com>
> From: David Marchand [mailto:david.marchand@redhat.com]
> Sent: Friday, 31 October 2025 14.12
>
> When debugging TSO and other checksum offloads, dumping the various
> l*_len fields and TSO segmentation size can be helpful.
>
> Example in OVS that dumps a mbuf on rte_eth_tx_prepare failure:
>
> Before:
> netdev_dpdk(pmd-c30/id:11)|DBG|dpdk0: First invalid packet:
> dump mbuf at 0x2201a916c0, iova=0x2200800580, buf_len=6864
> pkt_len=6804, ol_flags=0x3114800000000102, nb_segs=1, port=65535,
> ptype=0
> segment at 0x2201a916c0, data=0x22008005b2, len=6804, off=50,
> refcnt=1
> Dump data at [0x22008005b2], len=6804
> ...
>
> After:
> netdev_dpdk(pmd-c30/id:11)|DBG|dpdk0: First invalid packet:
> dump mbuf at 0x2201a916c0, iova=0x2200800580, buf_len=6864,
> pkt_len=6804
> outer_l2_len=14, outer_l3_len=40, l2_len=38, l3_len=40, l4_len=32,
> tso_segsz=0
> ol_flags=0x3114800000000102, nb_segs=1, port=65535, ptype=0
> segment at 0x2201a916c0, data=0x22008005b2, len=6804, off=50,
> refcnt=1
> Dump data at [0x22008005b2], len=6804
> ...
>
> Signed-off-by: David Marchand <david.marchand@redhat.com>
Good idea.
With or without suggested improvement inline below,
Acked-by: Morten Brørup <mb@smartsharesystems.com>
> ---
> lib/mbuf/rte_mbuf.c | 10 ++++++----
> 1 file changed, 6 insertions(+), 4 deletions(-)
>
> diff --git a/lib/mbuf/rte_mbuf.c b/lib/mbuf/rte_mbuf.c
> index 0d931c7a15..74dcb6c934 100644
> --- a/lib/mbuf/rte_mbuf.c
> +++ b/lib/mbuf/rte_mbuf.c
> @@ -750,10 +750,12 @@ rte_pktmbuf_dump(FILE *f, const struct rte_mbuf
> *m, unsigned dump_len)
>
> __rte_mbuf_sanity_check(m, 1);
>
> - fprintf(f, "dump mbuf at %p, iova=%#" PRIx64 ", buf_len=%u\n", m,
> rte_mbuf_iova_get(m),
> - m->buf_len);
> - fprintf(f, " pkt_len=%u, ol_flags=%#"PRIx64", nb_segs=%u,
> port=%u",
> - m->pkt_len, m->ol_flags, m->nb_segs, m->port);
> + fprintf(f, "dump mbuf at %p, iova=%#" PRIx64 ", buf_len=%u,
> pkt_len=%u\n",
> + m, rte_mbuf_iova_get(m), m->buf_len, m->pkt_len);
> + fprintf(f, " outer_l2_len=%u, outer_l3_len=%u, l2_len=%u,
> l3_len=%u, l4_len=%u, tso_segsz=%u\n",
> + m->outer_l2_len, m->outer_l3_len, m->l2_len, m->l3_len, m-
> >l4_len, m->tso_segsz);
Printing of outer_l2_len and outer_l3_len could be omitted if not present, like the VLAN IDs, e.g.:
fprintf(f, " ");
if (m->outer_l2_len != 0)
fprintf(f, "outer_l2_len=%u, ", m->outer_l2_len);
if (m->outer_l3_len != 0)
fprintf(f, "outer_l3_len=%u, ", m->outer_l3_len);
fprintf(f, "l2_len=%u, l3_len=%u, l4_len=%u, tso_segsz=%u\n",
m->l2_len, m->l3_len, m->l4_len, m->tso_segsz);
> + fprintf(f, " ol_flags=%#"PRIx64", nb_segs=%u, port=%u",
> + m->ol_flags, m->nb_segs, m->port);
>
> if (m->ol_flags & (RTE_MBUF_F_RX_QINQ | RTE_MBUF_F_TX_QINQ))
> fprintf(f, ", vlan_tci_outer=%u", m->vlan_tci_outer);
> --
> 2.51.0
next prev parent reply other threads:[~2025-10-31 13:28 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 13:11 David Marchand
2025-10-31 13:28 ` Morten Brørup [this message]
2025-10-31 14:07 ` David Marchand
2025-10-31 14:29 ` Morten Brørup
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=98CBD80474FA8B44BF855DF32C47DC35F65523@smartserver.smartshare.dk \
--to=mb@smartsharesystems.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
/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).