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 01F431BB81 for ; Fri, 13 Apr 2018 12:03:41 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 5AA0120D4E; Fri, 13 Apr 2018 06:03:41 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 13 Apr 2018 06:03:41 -0400 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=MCTi+uNAWLS+byvzqbO2rVlbDe GJGtfplVnY/ZIYQTA=; b=LPEj5ROelVfdM5HDk1oRdlZJxEDLV9O8UVHOpqZvn8 CM/RCQxfwKfZDY6+RlgZqPNIIQP1/A4VnoTjSru58BRaBu5pe8TmXhZb0uc9c1iL GKdZcdoMrCROLZeYw1dddbFsSnjN9m8yf269y4mpH12D5a/UTTwerQGtdpyskqJW c= 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=fm2; bh=MCTi+u NAWLS+byvzqbO2rVlbDeGJGtfplVnY/ZIYQTA=; b=imCKPJrATcyiitj+CJ5gv+ vp9l/YgM1UlI1cdW3D0PT+cfct58MkKmQ+d5RvIa4in+dFH8Gv5bmaozW82t7PC2 KSBwjZaYvGCh17b1fbUy/GK3btlc+ER8dXIzEpUJrthFDAKpX95DTGaDEMIAqXiW pTNbHgWWQ3inphaGo2FmYo3eZAphU0z2Hw9yOVPFXgYFcGn+pnh1i5isWeICVu+E eVwy691vnPMC3vff8FuBc3/Y8Mp0imLRFVwO41Dm7joYPoRtIGhSiwQMvdqPtrPr Z6ol/cHpcN9J2Bc/QnPFcUDReLNbrcfxZkJPBZX78woayG1XZrXmbTx7QCdhrnOA == 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 8FF13E4925; Fri, 13 Apr 2018 06:03:39 -0400 (EDT) From: Thomas Monjalon To: Jeff Guo Cc: dev@dpdk.org, stephen@networkplumber.org, bruce.richardson@intel.com, ferruh.yigit@intel.com, konstantin.ananyev@intel.com, gaetan.rivet@6wind.com, jingjing.wu@intel.com, motih@mellanox.com, harry.van.haaren@intel.com, jianfeng.tan@intel.com, shreyansh.jain@nxp.com, helin.zhang@intel.com Date: Fri, 13 Apr 2018 12:03:38 +0200 Message-ID: <1662267.QzXHl4zxrY@xps> In-Reply-To: <1523608240-9754-1-git-send-email-jia.guo@intel.com> References: <1498711073-42917-1-git-send-email-jia.guo@intel.com> <1523608240-9754-1-git-send-email-jia.guo@intel.com> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH V22 0/4] add device event monitor framework 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 10:03:42 -0000 13/04/2018 10:30, Jeff Guo: > About hot plug in dpdk, We already have proactive way to add/remove devices > through APIs (rte_eal_hotplug_add/remove), and also have fail-safe driver > to offload the fail-safe work from the app user. But there are still lack > of a general mechanism to monitor hotplug event for all driver, now the > hotplug interrupt event is diversity between each device and driver, such > as mlx4, pci driver and others. > > Use the hot removal event for example, pci drivers not all exposure the > remove interrupt, so in order to make user to easy use the hot plug > feature for pci driver, something must be done to detect the remove event > at the kernel level and offer a new line of interrupt to the user land. > > Base on the uevent of kobject mechanism in kernel, we could use it to > benefit for monitoring the hot plug status of the device which not only > uio/vfio of pci bus devices, but also other, such as cpu/usb/pci-express bus devices. [...] > Jeff Guo (4): > eal: add device event handle in interrupt thread > eal: add device event monitor framework > eal/linux: uevent parse and process > app/testpmd: enable device hotplug monitoring Applied, thanks