From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from out1-smtp.messagingengine.com (out1-smtp.messagingengine.com [66.111.4.25]) by dpdk.org (Postfix) with ESMTP id D24BF31FC for ; Mon, 15 Jan 2018 12:33:19 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 5D6EF20B1F; Mon, 15 Jan 2018 06:33:19 -0500 (EST) Received: from frontend1 ([10.202.2.160]) by compute1.internal (MEProxy); Mon, 15 Jan 2018 06:33:19 -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=HnJme4B8cOi4Qk6dx0YXhi5SZw 9p8iRN4GI4LJazj68=; b=e00lEOCa56f797sypUnGR+Rop67wEl92JWMIAASaE5 plrPE3KbJgM4UC0HSBMBYZnCXvh9O7153zCUiAxKBtRaQeURzF6RP/LwNRfj/xZF /Q02zl4JE0SCQDYi87+QUOb6YnMCGlrRTHuS0Y8WMXuVDxmoe1+pHjCULf02I4Tz 4= 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=HnJme4 B8cOi4Qk6dx0YXhi5SZw9p8iRN4GI4LJazj68=; b=WMxZFqyvROzM8o1yMstPUi KD7ARqhG9o10MdE+N4uKj2Vx5CvRjeBqnsz0OoGNcUdukSSePbynQG4u8gNJnPfA FDpzsQPq8PpwlRkSVtbqK/wguyBf7V/HaDXTXqN86iPdytoOYOjJX7vGBGjSpyt1 BFGLpa+j6iJSQH1qbYY3pLP/dDZ3fBHsnuPaLJeLal+G+vGPIX+upYMtr6wafbTU f11+9WQc1k9AZw9xNss3fYoEPnirNZB3lDH2+vpGD7H/M5UFT7uh5idE0dhXVzIg fRLKiyxSwmyap4JqQcSYMTcLyqEk8lC/1hYdxuYQ2c4NnvOzQUa9xZaIGUY65/6Q == 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 0C6C97E43A; Mon, 15 Jan 2018 06:33:19 -0500 (EST) From: Thomas Monjalon To: "Guo, Jia" Cc: dev@dpdk.org, stephen@networkplumber.org, bruce.richardson@intel.com, ferruh.yigit@intel.com, gaetan.rivet@6wind.com, konstantin.ananyev@intel.com, jblunck@infradead.org, shreyansh.jain@nxp.com, jingjing.wu@intel.com, helin.zhang@intel.com, motih@mellanox.com Date: Mon, 15 Jan 2018 12:32:47 +0100 Message-ID: <3468196.BpI31Qveuv@xps> In-Reply-To: References: <1515575544-2141-3-git-send-email-jia.guo@intel.com> <6774704.u5U2Uf1Nb3@xps> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH V10 1/2] eal: add uevent monitor api and callback func 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: Mon, 15 Jan 2018 11:33:20 -0000 15/01/2018 11:55, Guo, Jia: > On 1/15/2018 7:16 AM, Thomas Monjalon wrote: > > Hi, > > > > 11/01/2018 15:05, Jeff Guo: > >> +/* A genaral callback for all registerd devices */ > > Typos: genaral, registerd > > > > So the callback is only for registered devices? > > What about hotplugged devices? > > the hotplugged devices is managed by the application, if it prior > registered and in the app's hotplug device list, will always be monitor > whenever it plug in and out. the eal only care about the registered > devices. I disagree. The application needs the EAL service to get notified of a new device plugged in. We should find a way to register the callback for all devices, including new ones.