From mboxrd@z Thu Jan  1 00:00:00 1970
From: Thomas Monjalon <thomas@monjalon.net>
Subject: Re: [PATCH v7 1/2] eal: add uevent monitor for hot plug
Date: Tue, 09 Jan 2018 11:47:56 +0100
Message-ID: <2803089.mJXnisXhBj@xps>
References: <1509567405-27439-3-git-send-email-jia.guo@intel.com>
 <6b97ebc5-1ec5-a724-a620-96b23b126d01@intel.com>
 <HE1PR05MB321268C2DEA09EAD28D19DC4D2100@HE1PR05MB3212.eurprd05.prod.outlook.com>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7Bit
Cc: Mordechay Haimovsky <motih@mellanox.com>, dev@dpdk.org,
 "stephen@networkplumber.org" <stephen@networkplumber.org>,
 "bruce.richardson@intel.com" <bruce.richardson@intel.com>,
 "ferruh.yigit@intel.com" <ferruh.yigit@intel.com>,
 "gaetan.rivet@6wind.com" <gaetan.rivet@6wind.com>,
 "konstantin.ananyev@intel.com" <konstantin.ananyev@intel.com>,
 "shreyansh.jain@nxp.com" <shreyansh.jain@nxp.com>,
 "jingjing.wu@intel.com" <jingjing.wu@intel.com>,
 "helin.zhang@intel.com" <helin.zhang@intel.com>,
 "harry.van.haaren@intel.com" <harry.van.haaren@intel.com>
To: "Guo, Jia" <jia.guo@intel.com>
Return-path: <dev-bounces@dpdk.org>
Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com
 [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id CD24E1B01B
 for <dev@dpdk.org>; Tue,  9 Jan 2018 11:48:21 +0100 (CET)
In-Reply-To: <HE1PR05MB321268C2DEA09EAD28D19DC4D2100@HE1PR05MB3212.eurprd05.prod.outlook.com>
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>

09/01/2018 11:31, Mordechay Haimovsky:
> From: Guo, Jia [mailto:jia.guo@intel.com]
> > On 1/9/2018 8:39 AM, Thomas Monjalon wrote:
> > > At last there is the kernel binding effort - this one will probably
> > > be ignored for 18.02, because it is another huge topic.
> > > Without bothering with kernel binding, we can at least remove a device,
> > > get a notification, and eventually re-add it. It is a good first step.
> > > Anyway your testpmd patch tests exactly this scenario (totally new
> > > devices are not seen).
> > 
> > i will  separate it for you all to benefit  for review.  for kernel
> > binding, i just let it automatically compare with the first time manually
> > binding, and it is the part of he hot plug flow. so i suggest to review
> > more about that if it is not side effect and workable, beg for keep on.
> 
> This will not work for Mellanox which uses several drivers and services
> in order to map the device and device queues to user space. For example, 
> the mlx4 PMD (PMD for ConnectX-3 devices) requires that mlx4_core mlx4_en
> and mlx4_ib drivers to be loaded, and for RDM -core user-space libraries
> and daemons to be loaded.

Yes automatic binding is a feature which requires more work.
It cannot be ready for 18.02.