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 498E65689 for ; Fri, 30 Jun 2017 11:06:06 +0200 (CEST) Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailout.nyi.internal (Postfix) with ESMTP id 95D6E2096F; Fri, 30 Jun 2017 05:06:04 -0400 (EDT) Received: from frontend2 ([10.202.2.161]) by compute1.internal (MEProxy); Fri, 30 Jun 2017 05:06:04 -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:x-sasl-enc; s=mesmtp; bh=EWvYHUpC4FxP028 r2wNi39hSze7+HGcC45ES+pw+BKo=; b=Om8gOXx2pMBiHjSIiYtTDRF7CTUsvOL MAojABVN2cU5gvBZFFHFiUYN93iTQ+IjdAvcET+vln19KxDluS85eh4dP39N1KI+ Rb02QLGdEKwYVPMLRw/iT5vE3WLYmQTDF0+N8TzY/0VylXTDk3zXB90fS4Ra++l2 e4s6g/0nE9Sw= 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:x-sasl-enc; s= fm1; bh=EWvYHUpC4FxP028r2wNi39hSze7+HGcC45ES+pw+BKo=; b=sJy9YdKr r9ZQ/SokNUZHu6eXlxPis3qlDziuuTwruCmNmbL0UuyH9Lg4OnNA/pzBZiHlsv8t bE61Cb2TrBN9ysRGuKe7dDhztv/YLkzyi7UW8fwUiStL3E1WYv5phKOisjHjIbVb NGaSRHKbYHcy8RhYHHT3g4NBSpdwK0GzHSbZKKKZPph3pYtZuqClKydbBN0ja+z4 CL7ZceQqHsRcuiLwXaf4YZDA3i3zCGdY8/kgG6C9n0a1CNU4GfrDlfUHFZu9N0MN h/UPdl6tl5CxC356Mjk7/l5ekDqwzsGx+7tEKm9+xCC38Bvxu1oGV1W6o7VsPvdF jmFWbJC5vHUvBA== X-ME-Sender: X-Sasl-enc: ml7CBhcz0dJp1wR8ufedhPJpEZmJxfpMh8IHRpAKo8dq 1498813564 Received: from xps.localnet (184.203.134.77.rev.sfr.net [77.134.203.184]) by mail.messagingengine.com (Postfix) with ESMTPA id 36D682479C; Fri, 30 Jun 2017 05:06:04 -0400 (EDT) From: Thomas Monjalon To: Jan Blunck Cc: dev@dpdk.org, gaetan.rivet@6wind.com, shreyansh.jain@nxp.com Date: Fri, 30 Jun 2017 11:06:03 +0200 Message-ID: <2830134.KdhWyS32Ir@xps> In-Reply-To: <20170629182206.1072-14-jblunck@infradead.org> References: <20170629182206.1072-1-jblunck@infradead.org> <20170629182206.1072-14-jblunck@infradead.org> MIME-Version: 1.0 Content-Transfer-Encoding: 7Bit Content-Type: text/plain; charset="us-ascii" Subject: Re: [dpdk-dev] [PATCH v7 13/15] eal: add hotplug add/remove functions 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, 30 Jun 2017 09:06:06 -0000 29/06/2017 20:22, Jan Blunck: > /** > + * Hotplug add a given device to a specific bus. > + * > + * @param busname > + * The bus name the device is added to. > + * @param devname > + * The device name. Based on this device name, eal will identify a driver > + * capable of handling it and pass it to the driver probing function. > + * @param devargs > + * Device arguments to be passed to the driver. > + * @return > + * 0 on success, negative on error. > + */ > +int rte_eal_hotplug_add(const char *busname, const char *devname, > + const char *devargs); After the hotplug, we may need to get the rte_device. Should we add a struct **rte_device as parameter, or should we add a helper function to get the rte_device from busname and devname?