[dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc
Takeshi T Yoshimura
TYOS at jp.ibm.com
Fri Aug 2 10:09:35 CEST 2019
-----David Marchand <david.marchand at redhat.com> wrote: -----
>To: Takeshi T Yoshimura <TYOS at jp.ibm.com>
>From: David Marchand <david.marchand at redhat.com>
>Date: 08/01/2019 06:47PM
>Cc: dev <dev at dpdk.org>, David Christensen <drc at linux.vnet.ibm.com>
>Subject: [EXTERNAL] Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in
>On Thu, Aug 1, 2019 at 10:46 AM Takeshi T Yoshimura <TYOS at jp.ibm.com>
>> > - Are the (below) devices bound to vfio-pci or any other kmod at
>this point of the init?
>> Yes, vfio-pci is bound to 0030:01:00.0 in the log.
>> > - Is the spdk_nvme driver loaded at this point?
>> No, spdk just attempts to initialize dpdk at this point.
>> After the initialization finishes, spdk probes the nvme driver.
>Do you mean that spdk registers its drivers after rte_eal_init() has
>Nothing should prevent from registering the drivers them before
>calling rte_eal_init(), did you try this?
>If the drivers are in the form of shared libraries (.so files), did
>you try to load them using the -d eal option?
SPDK apps have to call rte_eal_init() before registering drivers,
since the driver allocates DMA memory.
Do I have to change existing apps and spdk core to workaround this issue to use new versions of dpdk?
More information about the dev