From: Stephen Hemminger <stephen@networkplumber.org>
To: Long Li <longli@microsoft.com>
Cc: "dev@dpdk.org" <dev@dpdk.org>,
"stable@dpdk.org" <stable@dpdk.org>,
Matan Azrad <matan@nvidia.com>
Subject: Re: [EXTERNAL] Re: [RFC] net/vdev_netvsc: check for NetVSC device before auto-probe
Date: Mon, 23 Feb 2026 15:01:15 -0800 [thread overview]
Message-ID: <20260223150115.3b0c6aa6@phoenix.local> (raw)
In-Reply-To: <DS3PR21MB5735AEF2A98A5E9D57F508D8CE77A@DS3PR21MB5735.namprd21.prod.outlook.com>
On Mon, 23 Feb 2026 21:42:45 +0000
Long Li <longli@microsoft.com> wrote:
> >
> > This is not sufficient to fix the github problem.
> > The container still has an interface, and cloud-init has given it an address. But it
> > has no route to outside (in container).
> >
> > It looks like the whole automagic vdev_netvsc model is so brittle it should be
> > removed.
>
> Can we set up a default config of not auto probing net_vdev_netvsc? Or some kind of flags that says a driver should not be auto loaded.
>
> Most customers are running "vdev" arguments to load them in their DPDK application.
The problem is it runs in an initializer so it would have to be a build flag
rather than a runtime flag.
prev parent reply other threads:[~2026-02-23 23:01 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-22 20:48 [RFC] net/vdev_netvsc: check for NetVSC device before auto-probe Stephen Hemminger
2026-02-22 22:00 ` Stephen Hemminger
2026-02-23 21:42 ` [EXTERNAL] " Long Li
2026-02-23 23:01 ` Stephen Hemminger [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=20260223150115.3b0c6aa6@phoenix.local \
--to=stephen@networkplumber.org \
--cc=dev@dpdk.org \
--cc=longli@microsoft.com \
--cc=matan@nvidia.com \
--cc=stable@dpdk.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