From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out3-smtp.messagingengine.com (out3-smtp.messagingengine.com [66.111.4.27]) by dpdk.org (Postfix) with ESMTP id CD24E1B01B for ; Tue, 9 Jan 2018 11:48:21 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 4092B20C99; Tue, 9 Jan 2018 05:48:21 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Tue, 09 Jan 2018 05:48:21 -0500 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=monjalon.net; h= cc:content-transfer-encoding:content-type:date:from:in-reply-to :message-id:mime-version:references:subject:to:x-me-sender :x-me-sender:x-sasl-enc; s=mesmtp; bh=Vp7XI4Oeluqk3hizTbWyPtO83+ SPgjoI2x+Kls40AbA=; b=LM5qNcrpFCh5wCRDcK39Xckpg/HhyenhFKn17hqIAm cdGq40gRaRCGhNKgEYnYn3y3tri9nou85pDBdsxt5TgilC+XKGTxFElTSG0h2zJk llxGJji48zc13HBIBuU+uS/ELHURup8SwbDq6ZKzfGazn4mcdLB6Zgwbf9wTb2OG I= DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :date:from:in-reply-to:message-id:mime-version:references :subject:to:x-me-sender:x-me-sender:x-sasl-enc; s=fm1; bh=Vp7XI4 Oeluqk3hizTbWyPtO83+SPgjoI2x+Kls40AbA=; b=LhK9OcizpaJLN0WryuJFg0 LmgXu2yuu9D9s18TG9JttlWcV7Hc8ehfAL9Z1078knXOjgarsJnlF9g3Vgbrxbuq 6hEptflshpgE13M+CIE3w8NUNcO77jRdhIrCbWwSckmvyN3ZPfHWyGMBfAhATh+Z pcltsONzfxACNaHUfAMI9+P/XImjDWVq8SapdkiJxG63nYa5wplH68aW0vtIfJxT T9GegFgu3SNyVr6+7bGJbZMpXCz3Cuu3kppOR5FK9fZ4qG4A3pkqMI2x06ICVybB KfnfIx5p9SplTYGn5kSmpIWXgwSIkq6UggZNSa0twp1wMZsxBVNtRJAkJtLTFo4g == X-ME-Sender: Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id DBD5B7E354; Tue, 9 Jan 2018 05:48:20 -0500 (EST) From: Thomas Monjalon To: "Guo, Jia" Cc: Mordechay Haimovsky , dev@dpdk.org, "stephen@networkplumber.org" , "bruce.richardson@intel.com" , "ferruh.yigit@intel.com" , "gaetan.rivet@6wind.com" , "konstantin.ananyev@intel.com" , "shreyansh.jain@nxp.com" , "jingjing.wu@intel.com" , "helin.zhang@intel.com" , "harry.van.haaren@intel.com" Date: Tue, 09 Jan 2018 11:47:56 +0100 Message-ID: <2803089.mJXnisXhBj@xps> In-Reply-To: References: <1509567405-27439-3-git-send-email-jia.guo@intel.com> <6b97ebc5-1ec5-a724-a620-96b23b126d01@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v7 1/2] eal: add uevent monitor for hot plug 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: Tue, 09 Jan 2018 10:48:22 -0000 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.