From: Alan Beadle <ab.beadle@gmail.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: users@dpdk.org
Subject: Re: Corrupted payload when sending many individual mbufs in loop
Date: Tue, 4 Feb 2025 18:31:06 -0500 [thread overview]
Message-ID: <CANTAOdxZHKuYisWBjOLL_uu6OxDuzqY=C_q_XcspOuZ7Y6asTg@mail.gmail.com> (raw)
In-Reply-To: <20250204152635.19deced0@hermes.local>
> Are you using refcounting of the mbuf. Are you reusing the data?
> DPDK has no callback or mechanism to indicate when data has actually been
> sent; ie the mbuf may still be in use for some amount of time while sitting
> in the device transmit queue and being DMA'd. Fragmenting can be complex
> to do.
Unlike my earlier threads, in this case I am not saving any mbufs nor
am I doing anything at all with the refcount. For retries I am
regenerating the lost packet from scratch each time. The problem is
that at high tx rates the payload is getting corrupted and I have no
idea why.
next prev parent reply other threads:[~2025-02-04 23:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-04 22:36 Alan Beadle
2025-02-04 23:26 ` Stephen Hemminger
2025-02-04 23:31 ` Alan Beadle [this message]
2025-02-05 12:13 ` Alan Beadle
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='CANTAOdxZHKuYisWBjOLL_uu6OxDuzqY=C_q_XcspOuZ7Y6asTg@mail.gmail.com' \
--to=ab.beadle@gmail.com \
--cc=stephen@networkplumber.org \
--cc=users@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).