DPDK patches and discussions
 help / color / mirror / Atom feed
From: Bruce Richardson <bruce.richardson@intel.com>
To: Thomas Monjalon <thomas@monjalon.net>
Cc: Stephen Hemminger <sthemmin@microsoft.com>,
	dev@dpdk.org, Stephen Hemminger <stephen@networkplumber.org>
Subject: Re: [dpdk-dev] [PATCH 2/3] usertools: add hv_uio_setup script
Date: Thu, 5 Apr 2018 22:07:34 +0100	[thread overview]
Message-ID: <20180405210734.GA85168@bricha3-MOBL.ger.corp.intel.com> (raw)
In-Reply-To: <1607753.vleKbttEpa@xps>

On Thu, Apr 05, 2018 at 10:43:39PM +0200, Thomas Monjalon wrote:
> 05/04/2018 21:13, Stephen Hemminger:
> > Small script to rebind netvsc kernel device to Hyper-V
> > networking PMD. It could be integrated in dpdk-bind, but dpdk-bind
> > is focused on PCI, and that would get messy.
> > 
> > Eventually, this functionality will be built into netvsc driver
> > (see vdev_netvsc as an example).
> 
> I believe we should avoid creating such script.
> The direction to go, for hotplug, is to remove dpdk-devbind.py,
> and implement kernel binding in PMDs (with EAL helpers).
>
I'm not convinced at all that that is the direction to go. I instead would
prefer to see all binding happen outside DPDK. I believe having udev or
similar manage bindings, set up via e.g driverctl[1], is a far better path.

Just my 2c.
/Bruce

[1] https://gitlab.com/driverctl/driverctl

  parent reply	other threads:[~2018-04-05 21:08 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-05 19:13 [dpdk-dev] [PATCH 0/3] add Hyper-V bus and network driver Stephen Hemminger
2018-04-05 19:13 ` [dpdk-dev] [PATCH 1/3] bus/vmbus: add hyper-v virtual bus support Stephen Hemminger
2018-04-05 19:13 ` [dpdk-dev] [PATCH 2/3] usertools: add hv_uio_setup script Stephen Hemminger
2018-04-05 20:43   ` Thomas Monjalon
2018-04-05 21:03     ` Stephen Hemminger
2018-04-05 21:13       ` Thomas Monjalon
2018-04-05 21:18         ` Stephen Hemminger
2018-04-05 21:20         ` Stephen Hemminger
2018-04-05 22:39         ` Stephen Hemminger
2018-04-05 21:07     ` Bruce Richardson [this message]
2018-04-05 21:10       ` Thomas Monjalon
2018-04-05 22:43         ` Stephen Hemminger
2018-04-05 23:57         ` Ananyev, Konstantin
2018-04-06  0:22           ` Stephen Hemminger
2018-04-06  8:38             ` Bruce Richardson
2018-04-05 19:13 ` [dpdk-dev] [PATCH 3/3] net/netvsc: add hyper-v netvsc network device Stephen Hemminger
2018-04-05 20:52   ` Thomas Monjalon
2018-04-05 20:59     ` Stephen Hemminger
2018-04-05 21:07       ` Thomas Monjalon
2018-04-05 21:19         ` Stephen Hemminger

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=20180405210734.GA85168@bricha3-MOBL.ger.corp.intel.com \
    --to=bruce.richardson@intel.com \
    --cc=dev@dpdk.org \
    --cc=stephen@networkplumber.org \
    --cc=sthemmin@microsoft.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 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).