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 631AC1B2F3 for ; Wed, 17 Jan 2018 22:59:46 +0100 (CET) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id E33D220C5F; Wed, 17 Jan 2018 16:59:44 -0500 (EST) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Wed, 17 Jan 2018 16:59:44 -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=8A2xX3hraxmsVHjwZjan1CTTcR V0zntpzWXscUDt+dM=; b=MzBocpG4rT78LR0+fL6cuya2TKKnPtb0P5OgphS5CA SYXOGBCuJDoM3x9PTyIorIZKc2wsu7SyDTgbhh6q75uLK11sv4YHDHqQDKDfawTX VPEONcmpu7VByF2V1LPHnOEzL2Tx7ljgD203prevg1jujJEHddQ620YphxOfPK6W A= 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=8A2xX3 hraxmsVHjwZjan1CTTcRV0zntpzWXscUDt+dM=; b=dFmKB0WlYj40HhsBxiAn8u JWltnc39yaKBhyvtZrRKeADko6Wid2XD7r8RSx+xhOVUAxBoVLcsrCzddsFVh9PF mjm22/XAg8OgqFe/5m1jHx5lv1hxpXHLig0j/8zv+DBMyTmt1TOXcSWX6feVmOR+ C1M6KH/EEMZOPxabAAHBO4hL3l9J8dckJlLbP0uOaY0FR81oAsHiZ9Qt3+bkupvM Q8dyRHK+mMynk1YyhCdb1sxtSrlTh6W/HZxL/7+vS66vsXCjWi/0AVDBa22CzZl2 qCJCBLXSTFFt5Xj5u7s35tbwDGzgmieLFflXDKPOKU587l4ceTF/FpttDs2ccltA == 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 84502246E6; Wed, 17 Jan 2018 16:59:44 -0500 (EST) From: Thomas Monjalon To: Jeff Guo 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: Wed, 17 Jan 2018 22:59:10 +0100 Message-ID: <10337288.PlhJV8PepH@xps> In-Reply-To: <1516013331-18939-1-git-send-email-jia.guo@intel.com> References: <1515679534-22473-2-git-send-email-jia.guo@intel.com> <1516013331-18939-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 V11 1/3] 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: Wed, 17 Jan 2018 21:59:46 -0000 15/01/2018 11:48, Jeff Guo: > + * It registers the callback for the specific event. Multiple > + * callbacks cal be registered at the same time. > + * > + * @param device_name > + * The device name. > + * @param cb_fn > + * callback address. > + * @param cb_arg > + * address of parameter for callback. > + * > + * @return > + * - On success, zero. > + * - On failure, a negative value. > + */ > +int rte_dev_callback_register(char *device_name, rte_dev_event_cb_fn cb_fn, > + void *cb_arg); What is the device name? I think we should register a callback for a rte_device or NULL (all devices).