From: 段世博 <duanshibo.d@gmail.com>
To: users@dpdk.org
Subject: Use external_buffer by ret_pktmbuf_attach on dpaa2 device
Date: Mon, 21 Apr 2025 10:16:23 +0800 [thread overview]
Message-ID: <CAEPTqQbvisu=wGX6pfkDEQG1k=W6_kBBk4wvLXNvQ7Bs5-5pDg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 608 bytes --]
Hello everyone, we want to use external_buffer on the dpaa2 nic, but when I
use rte_pktmbuf_attach, the network card cannot read the content of
external_buffer correctly. When I map this external_buffer through
rte_fslmc_vfio_mem_dmamap (an internal function), the network card can read
the data normally, but I don’t know if there is a problem with this use
(some restrictions that are not considered?). If this use is legal, I hope
that developers can add dma_map and dma_unmap functions in rte_fslmc_bus,
so that memory mapping can be completed by calling rte_dev_dma_map. Thank
you very much.
[-- Attachment #2: Type: text/html, Size: 621 bytes --]
reply other threads:[~2025-05-05 12:53 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAEPTqQbvisu=wGX6pfkDEQG1k=W6_kBBk4wvLXNvQ7Bs5-5pDg@mail.gmail.com' \
--to=duanshibo.d@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).