DPDK patches and discussions
 help / color / mirror / Atom feed
* When tap PMD is used, memory loss occurs in secondary block
@ 2021-12-16 20:28 Learn DPDK
  0 siblings, 0 replies; only message in thread
From: Learn DPDK @ 2021-12-16 20:28 UTC (permalink / raw)
  To: Learn DPDK, dev

[-- 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 --]

^ permalink raw reply	[flat|nested] only message in thread

only message in thread, other threads:[~2021-12-16 20:29 UTC | newest]

Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-12-16 20:28 When tap PMD is used, memory loss occurs in secondary block Learn DPDK

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).