From: Learn DPDK <learndpdk@gmail.com>
To: Learn DPDK <learndpdk@gmail.com>, dev@dpdk.org
Subject: When tap PMD is used, memory loss occurs in secondary block
Date: Thu, 16 Dec 2021 12:28:50 -0800 [thread overview]
Message-ID: <CAMxN_nAfvxiX6Ldb4GbN3_-9h8VcRP=oo2F90N15yDf_fY=HUA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 753 bytes --]
Hello.
Thanks a lot in advance for your help and nice support.
We use tap PMD to send exception packet to kernel by DPDK primary block.
If the secondary block is driven in this state, vdev probe is
performed inside rte_eal_init
func
and memory is allocated using the rte_zmalloc_socket function if it is
a secondary block in the rte_pmd_tap_probe
(dpdk-20.11/drivers/net/tap/rte_eth_tap.c) function.
The secondary block mentioned is used to debug the primary
block and is terminated immediately after executing the command so
the memory allocated above is not free and is lost.
The secondary block does not access the tap interface,
is there any way to prevent memory allocation for tap vdev?
I am inquiring this because rte_eth_tap.c file copyrighted
[-- Attachment #2: Type: text/html, Size: 2224 bytes --]
reply other threads:[~2021-12-16 20:29 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='CAMxN_nAfvxiX6Ldb4GbN3_-9h8VcRP=oo2F90N15yDf_fY=HUA@mail.gmail.com' \
--to=learndpdk@gmail.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).