From: "Takeshi T Yoshimura" <TYOS@jp.ibm.com>
To: David Marchand <david.marchand@redhat.com>
Cc: dev <dev@dpdk.org>, David Christensen <drc@linux.vnet.ibm.com>,
anatoly.burakov@intel.com
Subject: Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in ppc
Date: Fri, 2 Aug 2019 08:09:35 +0000 [thread overview]
Message-ID: <OF721626C6.2E6D78C9-ON0025844A.002CCF91-0025844A.002CD2B1@notes.na.collabserv.com> (raw)
In-Reply-To: <CAJFAV8zxYagNVmV2Xf2LCMG7QG7XFPNbDNJyZyEC+WeSaHiZtw@mail.gmail.com>
-----David Marchand <david.marchand@redhat.com> wrote: -----
>To: Takeshi T Yoshimura <TYOS@jp.ibm.com>
>From: David Marchand <david.marchand@redhat.com>
>Date: 08/01/2019 06:47PM
>Cc: dev <dev@dpdk.org>, David Christensen <drc@linux.vnet.ibm.com>
>Subject: [EXTERNAL] Re: [dpdk-dev] [PATCH] eal: forcing IOVA as PA in
>ppc
>
>On Thu, Aug 1, 2019 at 10:46 AM Takeshi T Yoshimura <TYOS@jp.ibm.com>
>wrote:
>>
>> > - 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
>returned?
>
>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?
>
>
>--
>David Marchand
>
>
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?
next prev parent reply other threads:[~2019-08-02 8:09 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-31 3:35 Takeshi Yoshimura
2019-07-31 9:10 ` Burakov, Anatoly
2019-07-31 9:29 ` David Marchand
2019-07-31 10:34 ` Takeshi T Yoshimura
2019-07-31 10:44 ` Takeshi T Yoshimura
2019-07-31 10:58 ` David Marchand
2019-07-31 19:23 ` David Christensen
2019-07-31 19:32 ` David Marchand
2019-07-31 21:20 ` David Christensen
2019-08-01 5:04 ` David Marchand
2019-07-31 19:44 ` David Marchand
2019-08-01 4:10 ` Takeshi T Yoshimura
2019-08-01 5:01 ` David Marchand
2019-08-01 5:25 ` Takeshi T Yoshimura
2019-08-01 7:15 ` David Marchand
2019-08-01 8:46 ` Takeshi T Yoshimura
2019-08-01 9:46 ` David Marchand
2019-08-02 8:09 ` Takeshi T Yoshimura [this message]
2019-08-02 8:22 ` David Marchand
2019-08-01 4:12 ` Takeshi T Yoshimura
2019-08-01 13:01 ` David Marchand
2019-08-02 8:50 ` Burakov, Anatoly
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=OF721626C6.2E6D78C9-ON0025844A.002CCF91-0025844A.002CD2B1@notes.na.collabserv.com \
--to=tyos@jp.ibm.com \
--cc=anatoly.burakov@intel.com \
--cc=david.marchand@redhat.com \
--cc=dev@dpdk.org \
--cc=drc@linux.vnet.ibm.com \
/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).