From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mails.dpdk.org (mails.dpdk.org [217.70.189.124]) by inbox.dpdk.org (Postfix) with ESMTP id C643E4308A; Thu, 17 Aug 2023 06:29:22 +0200 (CEST) Received: from mails.dpdk.org (localhost [127.0.0.1]) by mails.dpdk.org (Postfix) with ESMTP id 1247F43275; Thu, 17 Aug 2023 06:28:37 +0200 (CEST) Received: from dfw.source.kernel.org (dfw.source.kernel.org [139.178.84.217]) by mails.dpdk.org (Postfix) with ESMTP id E301243261 for ; Thu, 17 Aug 2023 06:28:29 +0200 (CEST) Received: from smtp.kernel.org (relay.kernel.org [52.25.139.140]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by dfw.source.kernel.org (Postfix) with ESMTPS id A9CB0619BF for ; Thu, 17 Aug 2023 04:28:29 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id D18DAC433CA; Thu, 17 Aug 2023 04:28:28 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1692246509; bh=xGiN+ZQQkb7KO9tfzNRbT96N4OAfikuDuzqfaiDb67E=; h=From:To:Cc:Subject:Date:In-Reply-To:References:From; b=MvPINgS1yG2xaObod3qdWogtW+tVQp1hWuvy6OqDijqDmaL4/miOah4+olMqoqzEQ 1/JXU6Ic8sS7jfHnzY0UEq/2wRiTp7olM8aO1KE/6rbFysc1IHMQ+cNO1HEr820yxr S0Cor2C/Xbe55LzocNIwcrT+4c4tnR8eGw+ChKeh6EMlXgWqHRcbagqyVUeA+8zD7r 3CcJXf9K5JeWw/gdrfjiKxN7tnSvShSDTM/qAPRvqvOQf0rz2juF9G+O2hQf22M0Qb z6M9koWdtlI6jZHpoGCRXl+MGfgDM03l03g2A+Y8v+svuzVmsPfGi8Q/xHdj+ctfac TnAIYh+dn8P5A== From: okaya@kernel.org To: Cc: dev@dpdk.org, Sinan Kaya Subject: [PATCH v5 09/10] eal: declare the reinit via cleanup/init feature unsupported Date: Thu, 17 Aug 2023 00:28:20 -0400 Message-Id: <20230817042820.137957-10-okaya@kernel.org> X-Mailer: git-send-email 2.25.1 In-Reply-To: <20230817042820.137957-1-okaya@kernel.org> References: <20230817042820.137957-1-okaya@kernel.org> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-BeenThere: dev@dpdk.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: DPDK patches and discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: dev-bounces@dpdk.org From: Sinan Kaya Call of rte_eal_init() api after rte_eal_cleanup() possible for certain application types but this is not an officially supported feature. Signed-off-by: Sinan Kaya --- lib/eal/include/rte_eal.h | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/lib/eal/include/rte_eal.h b/lib/eal/include/rte_eal.h index 53c4a5519e..348b340f00 100644 --- a/lib/eal/include/rte_eal.h +++ b/lib/eal/include/rte_eal.h @@ -67,6 +67,11 @@ int rte_eal_iopl_init(void); * as possible in the application's main() function. * It puts the WORKER lcores in the WAIT state. * + * @warning + * It maybe possisble to call it again after rte_eal_cleanup(). + * But this usage is dependent on libraries and drivers support which + * may not work. Use at your own risk. + * * @param argc * A non-negative value. If it is greater than 0, the array members * for argv[0] through argv[argc] (non-inclusive) shall contain pointers -- 2.25.1