From: Bruce Richardson <bruce.richardson@intel.com>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: Ferruh Yigit <ferruh.yigit@intel.com>,
"Burakov, Anatoly" <anatoly.burakov@intel.com>,
dev@dpdk.org
Subject: Re: [dpdk-dev] DPDK driver autoloading?
Date: Thu, 14 Oct 2021 09:43:00 +0100 [thread overview]
Message-ID: <YWftlC4ag5A3Xx5h@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <20211013095218.6ced99fa@hermes.local>
On Wed, Oct 13, 2021 at 09:52:18AM -0700, Stephen Hemminger wrote:
> The current DPDK PCI code requires that all PMD shared libraries
> be loaded before probing. This a burden for applications that run
> on multiple platforms and a total mess for Linux distributions.
>
> A better way would be to have the bus scanning code autoload
> drivers as needed. This would work like the Linux kernel
> module loading.
>
> Could existing pmdinfogen mechanism be extended to to do this?
Can you clarify a bit more about what the problem is here? How does EAL
loading the modules first make things a mess for distributions, compared to
loading them on-demand? With both schemes you naturally need to ensure all
needed drivers are present, and can remove any unneeded drivers. The only
difference is that with our current scheme some unneeded drivers which are
present will be loaded at runtime but idle/unused - hardly a massive
impact, I would think. What am I missing here?
/Bruce
prev parent reply other threads:[~2021-10-14 8:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-13 16:52 Stephen Hemminger
2021-10-14 8:43 ` Bruce Richardson [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=YWftlC4ag5A3Xx5h@bricha3-MOBL.ger.corp.intel.com \
--to=bruce.richardson@intel.com \
--cc=anatoly.burakov@intel.com \
--cc=dev@dpdk.org \
--cc=ferruh.yigit@intel.com \
--cc=stephen@networkplumber.org \
/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).