From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mga03.intel.com (mga03.intel.com [134.134.136.65]) by dpdk.org (Postfix) with ESMTP id 196FB1C699 for ; Fri, 13 Apr 2018 18:40:52 +0200 (CEST) X-Amp-Result: UNSCANNABLE X-Amp-File-Uploaded: False Received: from orsmga007.jf.intel.com ([10.7.209.58]) by orsmga103.jf.intel.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 13 Apr 2018 09:40:51 -0700 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.48,446,1517904000"; d="scan'208";a="33178540" Received: from bricha3-mobl.ger.corp.intel.com ([10.252.21.150]) by orsmga007.jf.intel.com with SMTP; 13 Apr 2018 09:40:47 -0700 Received: by (sSMTP sendmail emulation); Fri, 13 Apr 2018 17:40:46 +0100 Date: Fri, 13 Apr 2018 17:40:46 +0100 From: Bruce Richardson To: Thomas Monjalon 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 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 Content-Disposition: inline In-Reply-To: <2407757.yEAnF6RcS7@xps> Organization: Intel Research and Development Ireland Ltd. User-Agent: Mutt/1.9.4 (2018-02-28) Subject: Re: [dpdk-dev] kernel binding of devices + hotplug X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.15 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Apr 2018 16:40:53 -0000 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