From mboxrd@z Thu Jan  1 00:00:00 1970
From: Bruce Richardson <bruce.richardson@intel.com>
Subject: Re: kernel binding of devices + hotplug
Date: Fri, 13 Apr 2018 17:40:46 +0100
Message-ID: <20180413164046.GD37024@bricha3-MOBL.ger.corp.intel.com>
References: <2407757.yEAnF6RcS7@xps>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: dev@dpdk.org, anatoly.burakov@intel.com, pmatilai@redhat.com,
 david.marchand@6wind.com, jia.guo@intel.com, matan@mellanox.com,
 konstantin.ananyev@intel.com, stephen@networkplumber.org, fbl@redhat.com
To: Thomas Monjalon <thomas@monjalon.net>
Return-path: <dev-bounces@dpdk.org>
Received: from mga03.intel.com (mga03.intel.com [134.134.136.65])
 by dpdk.org (Postfix) with ESMTP id 196FB1C699
 for <dev@dpdk.org>; Fri, 13 Apr 2018 18:40:52 +0200 (CEST)
Content-Disposition: inline
In-Reply-To: <2407757.yEAnF6RcS7@xps>
List-Id: DPDK patches and discussions <dev.dpdk.org>
List-Unsubscribe: <https://dpdk.org/ml/options/dev>,
 <mailto:dev-request@dpdk.org?subject=unsubscribe>
List-Archive: <http://dpdk.org/ml/archives/dev/>
List-Post: <mailto:dev@dpdk.org>
List-Help: <mailto:dev-request@dpdk.org?subject=help>
List-Subscribe: <https://dpdk.org/ml/listinfo/dev>,
 <mailto:dev-request@dpdk.org?subject=subscribe>
Errors-To: dev-bounces@dpdk.org
Sender: "dev" <dev-bounces@dpdk.org>

On Fri, Apr 13, 2018 at 06:31:21PM +0200, Thomas Monjalon wrote:
> It's time to think (again) how we bind devices with kernel modules.
> We need to decide how we want to manage hotplugged devices with DPDK.
> 
> A bit of history first.
> There was some code in DPDK for bind/unbind, but it has been removed
> in DPDK 1.7 - http://dpdk.org/commit/5d8751b83
> Copy of the commit message (in 2014):
> "
> 	The bind/unbind operations should not be handled by the eal.
> 	These operations should be either done outside of dpdk or
> 	inside the PMDs themselves as these are their problems.
> "
> 
> The question raised at this time (4 years ago) is still under discussion.
> Should we manage binding inside or outside DPDK?
> Should it be controlled in the application or in the OS base?
> 
> As you know, we use dpdk-devbind.py.
> This tool lacks two major features:
> 	- persistent configuration
> 	- hotplug
> 
> If we consider that the DPDK applications should be able to apply its own
> policy to choose the devices to bind, then we need to implement binding
> in the PMD (with EAL helpers).
> 
> On the other hand, if we consider that it is the system responsibility,
> then we could choose systemd/udev and driverctl.
> 
> The debate is launched!
> 

Allow me to nail my colours to the mast early! :-)

I believe it's system not application responsibility.
I also believe I have previously explained my reasons for that choice in
some of the previous email threads.

/Bruce