DPDK usage discussions
 help / color / mirror / Atom feed
From: narsimharaj pentam <pnarsimharaj@gmail.com>
To: users@dpdk.org
Subject: Indirect mbuf handling
Date: Tue, 9 Dec 2025 22:11:11 +0530	[thread overview]
Message-ID: <CAFLDJDprPRB8mjybypwuvHOEp+MfXjSK6W1YJD=Db2CURUhLNA@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 961 bytes --]

Hi

I have a query related to ip fragmentation handling in DPDK.

The DPDK application is trying to send a larger packet than the configured
MTU on the interface, before sending the packet to the  i40e PMD the packet
will
undergo fragmentation . The DPDK library function
*"rte_ipv4_fragment_packet"* is used for fragmentation. Function
*rte_ipv4_fragment_packet* will create
direct and indirect mbuf's  for a fragment , *the indirect buffers will
have reference to the mbuf of the actual packet (zero copy).*

The application will call function rte_eth_tx_burst to transmit fragments ,
which internally invokes *i40e_xmit_pkts *, the question here  is when
should main application
mbuf should be freed , can It be freed immediately  after i40e_xmit_pkts
returns success, not sure because the mbuf's are queued up in software ring
before actual transmit,
I am worried about the fragments holding references to the main application
buffer.

Thanks.

BR
Narsimha

[-- Attachment #2: Type: text/html, Size: 1168 bytes --]

             reply	other threads:[~2025-12-09 16:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-09 16:41 narsimharaj pentam [this message]
2025-12-09 17:05 ` narsimharaj pentam
2025-12-10  9:44   ` Morten Brørup
2025-12-10 11:41     ` narsimharaj pentam

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='CAFLDJDprPRB8mjybypwuvHOEp+MfXjSK6W1YJD=Db2CURUhLNA@mail.gmail.com' \
    --to=pnarsimharaj@gmail.com \
    --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).