From: Thomas Monjalon <thomas@monjalon.net>
To: Gaetan Rivet <gaetan.rivet@6wind.com>
Cc: dev@dpdk.org, Dirk-Holger Lenz <dirk.lenz@ng4t.com>
Subject: Re: [dpdk-dev] [PATCH v3] eal: read and parse device option separately
Date: Thu, 03 Aug 2017 19:57:41 +0200 [thread overview]
Message-ID: <5262738.FVJRLsIQ6H@xps> (raw)
In-Reply-To: <9208af1d05aa250b54f145aefbefaf070797dc90.1501693678.git.gaetan.rivet@6wind.com>
02/08/2017 19:10, Gaetan Rivet:
> When the EAL parses the common options given to the application,
> not all subsystems are available. Some device drivers are registered
> afterward upon dynamic plugin loading.
>
> Devices using those drivers are thus unable to be parsed by any drivers
> and are rejected.
>
> Store the device options first and keep them for later processing.
> Parse these right before initializing the buses, the drivers must have
> been stabilized at this point.
>
> Signed-off-by: Gaetan Rivet <gaetan.rivet@6wind.com>
> Tested-by: Dirk-Holger Lenz <dirk.lenz@ng4t.com>
Applied, thanks
prev parent reply other threads:[~2017-08-03 17:57 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-08-01 18:13 [dpdk-dev] [PATCH] " Gaetan Rivet
2017-08-02 8:56 ` [dpdk-dev] [PATCH v2] " Gaetan Rivet
2017-08-02 14:29 ` Thomas Monjalon
2017-08-02 15:23 ` Gaëtan Rivet
2017-08-02 17:10 ` [dpdk-dev] [PATCH v3] " Gaetan Rivet
2017-08-03 17:57 ` Thomas Monjalon [this message]
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=5262738.FVJRLsIQ6H@xps \
--to=thomas@monjalon.net \
--cc=dev@dpdk.org \
--cc=dirk.lenz@ng4t.com \
--cc=gaetan.rivet@6wind.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).