From: Stephen Hemminger <stephen@networkplumber.org>
To: Flavio Leitner <fbl@redhat.com>
Cc: Thomas Monjalon <thomas@monjalon.net>,
dev@dpdk.org, bruce.richardson@intel.com,
anatoly.burakov@intel.com, pmatilai@redhat.com,
david.marchand@6wind.com, jia.guo@intel.com, matan@mellanox.com,
konstantin.ananyev@intel.com
Subject: Re: kernel binding of devices + hotplug
Date: Wed, 18 Apr 2018 11:17:47 -0700 [thread overview]
Message-ID: <20180418111747.1a0033a1@xeon-e3> (raw)
In-Reply-To: <20180418141101.GB2549@plex.lan>
On Wed, 18 Apr 2018 11:11:01 -0300
Flavio Leitner <fbl@redhat.com> wrote:
> On Sun, Apr 15, 2018 at 01:48:36AM +0000, Stephen Hemminger wrote:
> > My vote is to work with udev and not try to replace it.
> >
> > Driverctl works well. Just not for bifurcated driver
>
> I second that. We also have other system configs to care about like
> kernel parameters and hugepage configuration which I think follow the
> same idea that they are system wide configs and should not be managed
> by DPDK itself.
Maybe teach driverctl (and udev) to handle bifurcated drivers.
Unfortunately, vendors are very fractured on how network devices are managed.
next prev parent reply other threads:[~2018-04-18 18:17 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-13 16:31 kernel binding of devices + hotplug Thomas Monjalon
2018-04-13 16:40 ` Bruce Richardson
2018-04-13 17:40 ` Burakov, Anatoly
2018-04-14 20:10 ` Matan Azrad
2018-04-16 8:31 ` Bruce Richardson
2018-04-16 16:11 ` Matan Azrad
2018-04-16 16:57 ` Stephen Hemminger
2018-04-16 17:10 ` Matan Azrad
2018-04-16 17:18 ` Stephen Hemminger
2018-04-16 17:32 ` Matan Azrad
2018-04-16 17:50 ` Thomas Monjalon
2018-04-17 9:23 ` Ananyev, Konstantin
2018-04-17 10:42 ` Matan Azrad
2018-04-17 11:00 ` Ananyev, Konstantin
2018-04-22 11:26 ` Matan Azrad
2018-04-16 9:26 ` Guo, Jia
2018-04-16 16:11 ` Matan Azrad
2018-04-15 5:01 ` Wiles, Keith
2018-04-15 1:48 ` Stephen Hemminger
2018-04-18 14:11 ` Flavio Leitner
2018-04-18 18:17 ` Stephen Hemminger [this message]
2018-04-18 18:54 ` Flavio Leitner
2018-04-19 6:04 ` Alejandro Lucero
2018-04-19 8:24 ` Thomas Monjalon
2018-04-19 8:40 ` Bruce Richardson
2018-04-19 9:47 ` Thomas Monjalon
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=20180418111747.1a0033a1@xeon-e3 \
--to=stephen@networkplumber.org \
--cc=anatoly.burakov@intel.com \
--cc=bruce.richardson@intel.com \
--cc=david.marchand@6wind.com \
--cc=dev@dpdk.org \
--cc=fbl@redhat.com \
--cc=jia.guo@intel.com \
--cc=konstantin.ananyev@intel.com \
--cc=matan@mellanox.com \
--cc=pmatilai@redhat.com \
--cc=thomas@monjalon.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.