From: "Morten Brørup" <mb@smartsharesystems.com>
To: "David Marchand" <david.marchand@redhat.com>, <dev@dpdk.org>
Subject: RE: [PATCH v2] mbuf: dump Tx offload metadata
Date: Tue, 4 Nov 2025 12:45:53 +0100 [thread overview]
Message-ID: <98CBD80474FA8B44BF855DF32C47DC35F6552D@smartserver.smartshare.dk> (raw)
In-Reply-To: <20251104100214.1818660-1-david.marchand@redhat.com>
> From: David Marchand [mailto:david.marchand@redhat.com]
> Sent: Tuesday, 4 November 2025 11.02
>
> 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
> 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>
> ---
Reviewed-by: Morten Brørup <mb@smartsharesystems.com>
next prev parent reply other threads:[~2025-11-04 11:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-31 13:11 [PATCH] " David Marchand
2025-10-31 13:28 ` Morten Brørup
2025-10-31 14:07 ` David Marchand
2025-10-31 14:29 ` Morten Brørup
2025-11-04 7:43 ` David Marchand
2025-11-04 10:02 ` [PATCH v2] " David Marchand
2025-11-04 11:45 ` Morten Brørup [this message]
2025-11-04 13:58 ` David Marchand
2025-11-04 18:45 ` 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=98CBD80474FA8B44BF855DF32C47DC35F6552D@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).