* [dpdk-dev] Issue/Question with multi-process and CryptoDev using AESNI_MB
@ 2021-03-11 19:36 Luse, Paul E
2021-03-23 15:11 ` Luse, Paul E
0 siblings, 1 reply; 2+ messages in thread
From: Luse, Paul E @ 2021-03-11 19:36 UTC (permalink / raw)
To: dev
Hi All,
I'm having an issue with the following scenario with SPDK-based applications built w/DPDK
using CryptoDev in a primary/secondary process setup.
Primary Process: An application that does crypto and properly initializes aesni_mb
Secondary Process: An application that does not use crypto so does not initialize aesni_mb
What I'm seeing:
1) Primary Process: Initializes normally
2) Secondary Process: At DPDK initialization time rte_eal_init()->rte_bus_scan()->vdev_scan()
Is called in that order and then in vdev_scan() there's a block of code that sends a msg to the primary
process to get device names that it's initialized so the secondary ends up adding the aesni
device and initializing it.
3) Process 2: Exits but because this SPDK application did not initialize crypto, it does
not call rte_vdev_uninit() so on exit gets several memory leaks from allocations
made during DPDK’s initialization of aesni, for example, alloc_mb_mgr()
It seems as though the secondary side should be tearing down aesni_mb assuming that
it was not the one who called rte_cryptodev_pmd_create() but I am fairly new to these
code sequences so am looking for some advice on what makes sense here to address the
issue.
thanks
Paul
^ permalink raw reply [flat|nested] 2+ messages in thread
* [dpdk-dev] Issue/Question with multi-process and CryptoDev using AESNI_MB
2021-03-11 19:36 [dpdk-dev] Issue/Question with multi-process and CryptoDev using AESNI_MB Luse, Paul E
@ 2021-03-23 15:11 ` Luse, Paul E
0 siblings, 0 replies; 2+ messages in thread
From: Luse, Paul E @ 2021-03-23 15:11 UTC (permalink / raw)
To: dev; +Cc: Harris, James R, Zawadzki, Tomasz
Hi All,
I'm having an issue with the following scenario with SPDK-based applications built w/DPDK
using CryptoDev in a primary/secondary process setup.
Primary Process: An application that does crypto and properly initializes aesni_mb
Secondary Process: An application that does not use crypto so does not initialize aesni_mb
What I'm seeing:
1) Primary Process: Initializes normally
2) Secondary Process: At DPDK initialization time rte_eal_init()->rte_bus_scan()->vdev_scan()
Is called in that order and then in vdev_scan() there's a block of code that sends a msg to the primary
process to get device names that it's initialized so the secondary ends up adding the aesni
device and initializing it.
3) Secondary Process: Exits but because this SPDK application did not initialize crypto, it does
not call rte_vdev_uninit() so on exit gets several memory leaks from allocations
made during DPDK’s initialization of aesni, for example, alloc_mb_mgr()
It seems as though the secondary side should be tearing down aesni_mb assuming that
it was not the one who called rte_cryptodev_pmd_create() but I am fairly new to these
code sequences so am looking for some advice on what makes sense here to address the
issue.
thanks
Paul
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2021-03-23 17:46 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2021-03-11 19:36 [dpdk-dev] Issue/Question with multi-process and CryptoDev using AESNI_MB Luse, Paul E
2021-03-23 15:11 ` Luse, Paul E
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).